Try Getting started with Data Management scripting. This walks you through running your first transfer, setting up filters, queries, and connection strings, running a simple cleaning and weighting script, and gives suggestions on how to use the resources in the UNICOM Intelligence Developer Documentation Library to develop your skills.

There are no built-in limits to the number of Include statements you can use in your DMS files.

There are no built-in limits to the number of text substitutions you can define. Remember that you cannot use line-continuation characters in Include statements, so the text substitutions must be defined on one line. However, there is no practical limit to the number of characters in a line.

If you use the /x option in DMS Runner, it creates one of these files (called exception XML files) when the execution of a DMS file fails. In the event that you need to contact UNICOM Intelligence Technical Support because of the failure of a DMS file, you should send the exception XML file that relates to the failure. You should be able to identify the file using the numbers in the filename, which are in the form yyyymmdd_hhmmss and represent the date and time the file was written. (yyyy represents the year, mm the month, etc.) If you do not need to contact UNICOM Intelligence Technical Support, you can safely delete these files.

“Time elapsed” refers to the time taken to actually transfer the records and to run the OnJobStart, OnNextCase and OnJobEnd Event sections. This time is then used to calculate the number of records transferred per second. The “Time elapsed” does not include the time taken to validate the DMS file, merge and save the output metadata, run the OnBeforeJobStart, OnAfterMetaDataTransformation, and OnAfterJobEnd Event sections or any update queries, or initialize and close down the data sources.

The number of records transferred per second is not shown when the “Time elapsed” is less than one second.

If you type your connection strings in by hand (rather than generating them using the UNICOM Intelligence Professional Connection String Builder or WinDMSRun) make sure that you spell the Data Source connection property correctly. If you spell it as one word (DataSource) the DMS file might fail. This is a very easy mistake to make because the DataSource object in the MDM is one word, the InputDataSource section is one word, but the connection property is two words.