As others have said, there are a number of ways to do this. 1.  If you have the table defined in metadata, create  a new job, drop the table as a target on your job, add a Loader transform, and drop any source table that already exists as the source to the loader;  something like this :  source table -> loader -> target table Run the job, the target table will be created, and the source data will be loaded into it.  DI Studio will also create any keys or indexes that you have defined on your target table for you as part of that load process.  DI Studio will generate all of the appropriate code to create the table, columns, etc that you defined in metadata.  There are also various load techniques available in that loader, you can try various settings.  Base SAS tables typically should be replaced but you may want truncate for database tables.  2.  IF you are working with BASE SAS tables only, there is a nice feature in the data viewer that will actually create the base sas table if it doesnt exist and put you in edit mode so that you can begin adding data to it.  To do this, RMB on the Base sas table that does not exist, and say "Open".  If the physical table does not exist it will tell you that, ask if you want to create it.  Say yes and the table will get created as an empty table in the library where you selected the table to go to in the metadata definition.  The nice thing about this technique is it is essentially a shortcut way of creating base sas tables.  The same code that the loader generates is generated on the fly to create the table.  This only works for base sas tables.  ... View more

If you deploy to a workspace server instead of a stored process server those macros will be commented out.  When using the stored process wizard, just select a workspace server instead. Another option if you just want the job code without anything around it, is to select deploy for scheduling, which will generate the job code and put the code into a directory of your choice. Finally, if you want to just generate the code, in DI Studio 4.3 that shipped with 9.3, there is a command line feature that lets you deploy a job from a command line.  It will also just generate the job code and place it in a directory for you. Hope this helps. ... View more

Typically when everything is on the same machine these are the values I use for 9.2;  the port may be different for 9.1: hostname:  localhost port:  (enter a port number or use the default port 8561) userid:  your local userid;  needs to be valid for the host your metadata server is on password:  your local password; needs to be valid for the host your metadata server is on Authentication domain:  leave it blank or DefaultAuth ... View more

In 9.3 there is a new tool in the tools menu called the column propagation tool.  It will support modifying/standarizing one or more metadata columns downstream of a source column for all metadata attributes including formats, length, and other attributes.  Lineage is also available from the tool to help identify where a column is used.  It is still a visual tool, but it does help automate the mapping process when columns change.  We have captured your request for additional automated tools to help with this task and will consider more features in this area in a future release.  Thanks for the feedback.  ... View more

Thanks for the response.  Having use cases and details about them really helps us in scoping for future development.  We have captured your comments in our requirements management system, and we will investigate extending this feature set for the future.  ... View more

One way to try is to use the LOG option that will provide the name of the log file, which wont work if you are running interactively.  You can also specify the ALTLOG option if that helps.  ... View more

Here is an answer from development:  Correct, an information map can currently only wrap a single OLAP cube.  As for the multiple fact tables, a user would have to create a single fact table with the summarization of actual and forecast in one table.  They can achieve that result using the data step.  Then they can build the cube they want, and then use that in the map.  ... View more

The sort indicator is reset each time a table update occurs.  So in this case, even though you have sorted a source SAS data set prior to loading to the target, the target table does not inherit the sort indicator from the source table.  If the target table is actually in correct sort order as a result of loading a sorted source table, you can set the sort indicator to sorted=YES on the target using the SAS SORTEDBY data set option OR the datasets procedure MODIFY. Hope this helps. ... View more

There is no CWM export facility for jobs, only for tables and columns.  One possible way to get CWM job output using some programming would be to first export the job into the  .spk package file which contains the  full job XML if you include associated objects such as physical tables in it.  Then write an XSL conversion on the job XML in the spk package  to convert it to CWM format.  Development does this sort of thing when it does differencing of job XML for versioning, which is coming in the 9.3 release of DI Studio.  The 9.3 differencing facility pulls out the job XML from the .spk package content, and runs an XSL conversion on it to make the view more user friendly.  You could do something similar to convert to another format.  The OMR metadata format is loosely based on CWM structures, so there would be a fairly close correlation to CWM object types.  There has been a request to add this capability in the future, but no near term plans for it.  Hope this helps, nar@sas ... View more

This question should probably be posted to this discussion forum instead: http://support.sas.com/forums/forum.jspa?forumID=31 SAS Macro Facility, Data Step and SAS Language Elements They can probably help. ... View more

This is a little out of the scope of this forum, but here is some information. I suggest that questions like this in the future be posted to Base SAS dicussion forum rather than DI. ssd04 is a Unix V6 SAS Data Set This topic describes 9.2 support for V6 datasets and how to use them: http://support.sas.com/documentation/cdl/en/hostunx/61879/HTML/default/viewer.htm#a002256555.htm As per the doc above, there is a V6 read-only engine in 9.2. The data set has to be the same unix 'flavor' as the environment you are running. If you are not able to access the above link, then I suggest they open a track with SAS Technical Support and they will grant you access. ... View more

I have confirmed that we don't have any option that turns off some of these variables but not others. As one of the other users posted, you can choose to go "All User Written" in which case we won't generate any code, it is entirely up to the user to generate whatever code they want. You can go to "User written body" which causes DI Studio to generate the macros (all of the macros, not some of them) but not the body of the transform. Or you can go to all generated. We put a requirement in to consider additional options for the future. ... View more

I did check with the developer, and there is some thought that there hasnt been any code changes in the user name resolution since 9.1.3SP4 so this problem has been there for a while. There is a TS track logged on the issue, and we will investigate a fix for a future release. ... View more