Warning Suppression and migrating jobs to diffenet environme

DataDoctor · Post by **DataDoctor** » Wed Jul 21, 2010 11:58 am

I had warning in development environment and I suppressed those warning by adding rules using Add Rule to Message Handler. Now when I migrate this job to test environment, it throws same warnings. Is there any way, I can migrate message handler rules too. Or how do I handle this situation.

anbu · Post by **anbu** » Wed Jul 21, 2010 12:06 pm

You cannot migrate message handler rules in the job. You need to add the rules again in the job in Test.

kduke · Post by **kduke** » Wed Jul 21, 2010 2:11 pm

A lot of people edit DSParms. It is tricky to get it correct. It is in there twice. You need to always back these files up. Just copy it and add the current date to name. This way you can roll back if you mess it up. You can also lock down thes files and only allow admins to change them. Then copy the whole file from the dev server to the test server. This also needs a backup copy.

kduke · Post by **kduke** » Wed Jul 21, 2010 2:13 pm

Sorry the filename is DSParams. There is one per project.

ArndW · Post by **ArndW** » Thu Jul 22, 2010 5:50 am

Message handlers are stored in {YourPath}\IBM\InformationServer\Server\MsgHandlers and can be copied from one installation to another.

kduke · Post by **kduke** » Thu Jul 22, 2010 11:41 am

Arnd, is that version 8?

chulett · Post by **chulett** » Thu Jul 22, 2010 12:32 pm

Seems like it, I recall them being in "msh" files in each job's folder... under the "SC" directory, perhaps?

ray.wurlod · Post by **ray.wurlod** » Thu Jul 22, 2010 7:22 pm

Local message handlers are in the msh files.
Global (named) message handlers are in the directory Arnd mentioned.

You can migrate the files - they are pure text. The main issue is getting the correct msh file into the correct job SC directory on the target.

I believe istool is better at picking these up than is DataStage export/import.

highpoint · Post by **highpoint** » Wed Aug 25, 2010 10:13 am

ray.wurlod wrote:Local message handlers are in the msh files.
Global (named) message handlers are in the directory Arnd mentioned.

You can migrate the files - they are pure text. The main issue is getting the correct msh file into the correct job SC directory on the target.

I believe istool is better at picking these up than is DataStage export/import.

Hi,

I have the same problem for which this topic was created.

I have local message handlers for one of my job.They are lost in different environment and sometime in the same environment.

I am suspecting this is due to recompilation.

I would like to know if we deploy the job executable without job design then also will i get the same issue in the test environment?

And were are the msh files located?? And how do i move them to different environment.??

Appreciate reply.

mandyli · Post by **mandyli** » Wed Aug 25, 2010 1:47 pm

Just copy Message handler from DEV to QA or QA to Production.

All the nessage handlers stored in the following path with *.msh.

/opt/IBM/Engine/InformationServer/Server/MsgHandlers

Thanks
Man

highpoint · Post by **highpoint** » Wed Aug 25, 2010 3:33 pm

mandyli wrote:Just copy Message handler from DEV to QA or QA to Production.

All the nessage handlers stored in the following path with *.msh.

/opt/IBM/Engine/InformationServer/Server/MsgHandlers

Thanks
Man

Actually i am using version 7.5.2

highpoint · Post by **highpoint** » Fri Aug 27, 2010 11:42 am

highpoint wrote:
mandyli wrote:Just copy Message handler from DEV to QA or QA to Production.

All the nessage handlers stored in the following path with *.msh.

/opt/IBM/Engine/InformationServer/Server/MsgHandlers

Thanks
Man
Actually i am using version 7.5.2

Resolved. We exported executable along with job design and reimported in test environment. So this takes care of migration of message handlers as well.