Sorry if this has come up before but a search of the forum for +TI +parameter or +TI +properties as you would expect lists too many hits to be of any use for finding something specific.

What I am after is a complete (or nearly complete will do) listing of all defined technical TI process control properties that are encoded in the .pro file.
For example:
602=Process Name
562=DatasourceType
560=Parameter count & names
577=Datasource variable count and names
572=Prolog line count & code
573=Metadata line count & code
574=Data line count & code
575=Epilog line count & code

This must exist, ... somewhere. (Maybe not somewhere publicly documented by IBM but somewhere I'm sure)

The reason being I'm doing a directory compare for the code base of multiple server instances and rules is no problem but for TI processes there is a not of "white noise" which blocks out the actual signal. I need to know for which control parameters I can ignore changes and for which do I need to care about if they are different?

Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

Maybe someone will chip in with a full list. All I can offer is that the parameter I always ignore when comparing *.pro files is 565, which seems to be some hash/gibberish field whose contents change every time a TI is saved.

qml wrote:Maybe someone will chip in with a full list. All I can offer is that the parameter I always ignore when comparing *.pro files is 565, which seems to be some hash/gibberish field whose contents change every time a TI is saved.

Thanks, that one I know.

Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

CAVEAT - this info was certainly true in 9.5 but may be out of date. Could anyone who knows better please update it?

When comparing pro files you should look at what kind of datasource it is and then strip out anything that is only relevant to other data-sources. The reason for this is that they can be full of random values. TM1 is a C program and in C memory is not initialised to zero by the runtime when it is allocated. In the running TM1 server the TI process is represented by a data structure which starts out full of whatever gibberish previously occupied that area of memory. TM1 correctly initialises the parts of that structure that are relevant to the type of process and it leaves the rest as is. When it comes to save the process to disk it just dumps the lot. Every time you save a text file data source TI you could get a new value for the e.g. 801:ProcessDataSourceODBOCubeName, which is completely irrelevant.

Thank's Duncan. Useful information, I had observed that a process which start life as ODBC then get saved as VIEW or CHARACTERDELIMITED will forever retain the original DataSourceQuery variable as well as the ODBC connection variables. I didn't know that other non-used properties could just be random junk.

I was thinking of just limiting the compare to:
Parameter number of, names, default values & prompts
Datasource Type & Datasourcenameforserver
Variable number of & names
The 4 code tabs
Run with security access

Can anyone think of some other properties which you would deem essential for a compare? And anyone done this before and can share experience with whatever tool was used to do it?

Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

For what it is worth, I used Beyond Compare 4.0 and have a script that does exactly what you are wanting to do it seems. Only TIs with significant (i.e. ignores the white noise) variances show up in the results window.