PAULDCLARK
Well Known Member
Has anyone seen this? Client is at Xe SP20 XU6:
There are a number of subsystem jobs launched after the backup on a daily basis from the OneWorld scheduler.
Subsequent attempts to deploy packages to the server result in the scheduler kernal blocking the package deployment kernal, i.e. it doesn't respond to the request to release locks. The package deployment goes into SEMW status and the whole system basically freezes from then on.
Our current feeling is that because the scheduler tracks the jobs it launches, and the subsystems never end, the scheduler kernal can never release its locks and therefore block the package.
Has anyone deployed server packages whilst subsystem jobs are active, either called from the command line, the application or the scheduler? I'm sure it works if run from the command line or application but can't put my finger on exactly when I have seen it happening.
Thanks
There are a number of subsystem jobs launched after the backup on a daily basis from the OneWorld scheduler.
Subsequent attempts to deploy packages to the server result in the scheduler kernal blocking the package deployment kernal, i.e. it doesn't respond to the request to release locks. The package deployment goes into SEMW status and the whole system basically freezes from then on.
Our current feeling is that because the scheduler tracks the jobs it launches, and the subsystems never end, the scheduler kernal can never release its locks and therefore block the package.
Has anyone deployed server packages whilst subsystem jobs are active, either called from the command line, the application or the scheduler? I'm sure it works if run from the command line or application but can't put my finger on exactly when I have seen it happening.
Thanks