Issue in Jbase trigger

  • vijay.amirthraj@gmail.com
  • Topic Author
  • Offline
  • New Member
  • New Member
More
11 years 11 months ago #13148 by vijay.amirthraj@gmail.com
Issue in Jbase trigger was created by vijay.amirthraj@gmail.com
Hi All,

I am using two environments 'source and target'. I have connected both environments using net use.

I am able to write some file available in source to target environment. My requirement is also to update a table once the files are copied in target.For that, I have created a trigger in target. so that whenever file from source is written in target,the trigger updates the table.

The issue is the trigger is not working fine. on observation, the trigger is looking for the program in source itself. Though trigger is available in target, it looks in source.

Below are the steps which I am doing

1. Run a routine in source
2. source routine writes the files in target(using Q pointer)
3.Write of files in successful but the trigger in target doesnt work
4.The trigger in target is invoked and looks for routine in source instead of target itself though the routine is available in target and compiled as well

I expect the trigger should pick the routine in target itself so that It updates the table in target.

Could anyone suggest a solution for this?

Regards
Vijaya Amirtha Raj

Please Log in or Create an account to join the conversation.

More
11 years 11 months ago #13153 by wam
Replied by wam on topic Issue in Jbase trigger
dear source doesnt have control to update anything in target.
Its better to check at target system (may be some chrone job or a flag file)whenever your file copying mechanism completes then it should update any table etc.

Please Log in or Create an account to join the conversation.

More
11 years 11 months ago #13155 by jpb
Replied by jpb on topic Issue in Jbase trigger
I have no experience with "net use" as we work on Unix, but I suppose the routine is invoked in the environment of the current user (source) because of the jBase variables.

If the user has execute permission also on target you can try to create a VOC for the routine in source as well, pointing explicitly to the target environment.

Maybe it works ...

Please Log in or Create an account to join the conversation.

Time to create page: 0.071 seconds