Was hoping someone from this community already encountered this before and know how to fix or workaround it?
Anybody setup tidal job on their datastage windows environment? There's no issue as long as the tidal scheduled jobs run fine but when the job fails, the connection between datastage engine and the WAS server will be broken with error code 81022 and users can not login to the DS environment until we reboot the DS engine server.
Also tried uninstalling the tidal agent on the DS engine server and it works overnight without issue (also run the same job via windows scheduler) and works okay. After reinstalling the newer version of tidal agent for windows... and run the tidal job, DS engine connection broken failure encountered again.
No issues with Unix just windows environment.
Also it maybe worth mentioning that the tidal agent is run as by the service id that has all the permission on the application and project forlders.
Tested this both on tidal agent for windows version 3.0.1.04 and 188.8.131.52 (newer version)
Tidal Master version is 5.3.1... Were just setting up our application environment to test on Tidal v6