Problem in importing one project jobs into another

Archive of postings to DataStageUsers@Oliver.com. This forum intended only as a reference and cannot be posted to.

Moderators: chulett, rschirm

Locked
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Problem in importing one project jobs into another

Post by admin »

DataStage problem,


We have two DataStage projects (dsproj and dsproj1) in a HP machine. Both projects are sharing the same DataStage server engine. We exported all jobs from dsproj and encountered errors when attempting to import these jobs into dsproj1. The error messages are as follows:

Error calling subroutine: DSR_JOB (Action=2); check DataStage is set up correctly in project dsproj1 (The connection is broken (81002))

Error calling subroutine: *DataStage*DSR_SELECT (Action=2); check DataStage is set up correctly in project dsproj1 (The connection is broken (81002))


We checked the server timeout option in the Administrator and confirmed that both projects server timeout values are set to adequate level (3600 seconds).

The above errors also occurred when we attempted to delete or save a job with a new job name. But no errors occurred when compiling and running jobs. All jobs ran were completed successfully.


On previous occcasions we did not have such errors when we imported jobs into dsproj1. The errors surfaced two days ago. Prior to this we had not done anything to dsproj1 except importing jobs into it and running a job now and then. No such problems were encountered in dsproj.

Does anyone has any idea what could be the cause of the above mentioned errors?


Thanks and Regards,
William

Disclaimer note:

Confidential information may be contained in this e-mail and any files transmitted with it (Message). If you are not the addressee indicated in this Message (or responsible for delivery of this Message to such person), you are hereby notified that any dissemination, distribution, printing or copying of this Message or any part thereof is strictly prohibited. In such a case, you should delete this Message immediately and advise the sender by return e-mail. Opinions, conclusions and other information in this Message that do not relate to the official business of Maxis shall be understood as neither given nor endorsed by Maxis.
Locked