Is it possible that the SAS Application Server that executes the job is not able to access the library where the macros are stored? If so, regsiter the librarty and assign it to the app server. ... View more

Hi Tushar, The DI Studio User Guide, which is available from the DI Studio help window and support.sas.com, has some basic information about scheduling jobs in the Deploying Jobs chapter. ... View more

In regard to explict versus implicit SQL pass-through . . . the DI Studio user guide has these two topics which might be relevant: http://support.sas.com/documentation/cdl/en/etlug/65807/HTML/default/viewer.htm#n1sqvkm1pyw3a1n1ik1ayutua5gu.htm http://support.sas.com/documentation/cdl/en/etlug/65807/HTML/default/viewer.htm#n0o4rbvvosnwran10wcv2e4ewyvd.htm ... View more

Jo, To read external files, see the DI Studio User Guide chapter "Working with External Files" : http://support.sas.com/documentation/cdl/en/etlug/62233/HTML/default/p0rhnqjrb6tje9n1jyfk9h4kn386.htm For all DI Studio doc related to DataFlux data quality . . . display the help in DI Studio, click the Search tab and search for "Working with Data Quality Transformations." For the creation of architech & profile jobs in dfPower Studio -- see dfPower Studio documentation. For how to reference df jobs into sas di -- see "Working with Data Quality Transformations" above. ... View more

The DI Studio 4.21 user guide has a topic that might be relevant. The topic is mainly about how to create a web service job, but it includes some subtopics about XML inputs and outputs in jobs that might be relevant to your case: http://support.sas.com/documentation/cdl/en/etlug/62233/HTML/default/n11c9v52jdl3ccn1r9niaolp1p2y.htm See "Create XML Libraries for the Inputs and Outputs" and "Register the XML Inputs and Outputs" ... View more

Does the "Connecting to Common Data Sources" chapter in the Data Administration Guide have a topic that matches your situation? http://support.sas.com/documentation/cdl/en/bidsag/61236/HTML/default/a003112367.htm ... View more

Yura, In most cases the source code is not stored in the metadata for each transformation in a DI Studio job. Usually the source code for each transformation is generated at runtime from the metadata. It is possible for user-written code to be specified for any transformation, and that user-written code can be stored in the metadata or in a file. But most jobs use transformations that generate the appropriate code at runtime, based on the metadata. Dave ... View more

The SAS Intelligence Platform: System Administration Guide has some general instructions for promoting jobs that might be helpful: http://support.sas.com/documentation/cdl/en/bisag/64088/HTML/default/viewer.htm#a003139354.htm ... View more

Sorry that did not help. If no one else posts a solution, a tech support call might be in order. ... View more

This is just a guess: if you right-click the job, do you see an Upgrade option? ... View more

Here's a topic that describes some special considerations when you are converting jobs from earlier releases to 9.2 (DI Studio 4.2). Do any of these conditions apply to your jobs that are not being converted? http://support.sas.com/documentation/cdl/en/whatsdiff/62095/HTML/default/viewer.htm#a003313387.htm ... View more

The SAS 9.2 Intelligence Platform: Data Administration Guide includes this topic about connecting to SAS/ACCESS via ODBC: http://support.sas.com/documentation/cdl/en/bidsag/61236/HTML/default/a003112372.htm ... View more

As suggested, large metadata repositories might cause a problem with a 32-bit OS. If you continue to have problems with large metadata repositories, consider contacting Tech Support. They might be able to say whether the methods described in this SAS Note would be appropriate in your situation: http://support.sas.com/kb/33/577.html I suggest that you check with Tech Support before trying this. ... View more

I think Linus is correct: you'd have to use the SQL Join transformation to do what you are talking about. Dave in SAS Publications ... View more