Originally posted by: SystemAdmin

I am currently testing the Beta release and have noticed that when running the Event Server with serarate system processes, each .mls file creates a task mercntsvns.exe which uses a minimum of around 10mb.
I have over 70 system files in my current 6.7 setup. If I run all of these as separate processes I will probably need to increase the memory in my server.
Has anyone had any experience with this version and should I combine my system files into super systems where the current msls are related to reduce the number of processes.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Your suggestoin is correct. Optimally, you won't want more than 4 or 5 event server processes, so combining common systems into one super system is the best way to go if you wish to run in separate processes.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

So if I were a customer like janhess is, and have 70+ msl files, I would have to i:e86f3a327fmanually[/i:e86f3a327f] combine those 70+ msl files into a couple of files. This seems to me like a b:e86f3a327fi:e86f3a327flot[/i:e86f3a327f][/b:e86f3a327f] of work so I don't run out of memory on the machine.
Is there a utility in 7.5 that allows me to merge msd files so there is not as much work that needs to go into the merging process of all of the overrides that I have in the system definition files?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

lews
I anticipate that by combining .msls I will still have around 20 systems.
I need to be able to run as separate processes in order to be able to control different systems easily. I currently run the multiple event server version of 6.7.1 and have 6 event servers. I also have a 6.5.1 event server which I would like to have split into 4 or 5 systems.
Is this too many for the event server to handle?

eric
I think the msds may be mergable by exporting them and merging parts of the xml - maybe I could write a map to do that.

Looks like quite a bit of work though to move to 7.5 and use separate processes in a large system. Perhaps the multiple event server version was an easier solution
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

janhess

If you were currently running that many Event Servers with 6.7.1 and 6.5.1, then I don't see an issue continuing with that many. I was just concerned with the amount of resources. The amount of resources for a single Event Server process in 7.5 should be equivalent to prior versions running the same systems.

As far as combining systems, you can also create a new system and drag and drop the different systems into the new parent system from within the IFD.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

More on combining...
1 - Create a new msd through the IFD.
2 - Select the "Add System" button from the floating toolbar and click in the system window the same as if you were adding a map
3 - Press the ... button beside the system name on the pop up dialog
4 - Go find an existing msd and select it
5 - If there are systems and subsystems in the selected msd, select only the systems from the component list. If you normally separate run maps from watch maps in your systems you should do this in this composite msd also.
6 - Repeat 2-5 for all msd's you want to combine
7 - Create your new deploy for this system of systems. If any of the combined msd's have "Additional Files" copies defined in their deploy scripts you will need to manually add these in.
8 - Get rid of the old msl's
9 - Deploy the new composite system of systems.

Note: The system of systems will be pointing to msd's in a specific source directory. It does not "follow" them if you move them. If you have different source directories for deploying to a test system vs. a production you will need to have separate "deployment" msd's. Alternatively, after step5 you can right mouse on the added system component(s) and change the "MSD" path to be relative.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Hi,

Testing with datastage TX 7.5 revealed for us the following :

we know that executing a lookup or extract on the same segments in a rule did not work with previous versions because of internal pointers. Now we find that there is an anomaly when having the same extract function but embedded in an IF or CHOOSE statement, so they are not suppose to execute both, yet none of them are executed now in version 7.5, although the map works fine in 6.5. Replacing the extract in the rule with fixed data reveals a perfectly working map and statement.

We are puzzled. Is 7.5 supposed to behave like this? Did you experience a similar feature?
Frank
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Frank - I haven't noticed any differences in the way handles series-consuming functions in 7.5, but my testing has been far from exhausting.

Were you aware that 7.5 is GA? You might want to get the released version from the download site and see if this turns out to be a defect that was repaired prior to the release.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange