Hello Suzm,
this behaviour is easy to explain.
When stoppin a jobsever, the schedulix server will not longer know the state of jobs currently executed by this jobserver.
So runing jobs will be be regarded as still running until the jobsever will start again and report the jobs state to the schedulix server again.
Cancelling a job which is still running will result in a CANCELLING state until the jobserver reports the job to be finished.
To solve your problem there are 3 possibilities:
1. Start your jobsever and wait until the job ist finished (or kill the job)
With the jobserver active again the state of the job will reported again.
2. Deregister the shutdown jobserver
This is a way of telling schedulix that the system is not longer up.
You ca do this in the GUI by selecting your jobserver in 'Jobserver and Resources' and pressing the 'Deregister' button (The one with the buring server).
All running jobs of this jobserver will be put into state 'BROKEN_FINISHED' since we do not have an exit state for those jobs in this case.
CANCELLING jobs will become CANCELLED then.
3. Alter the jobs state using sdmsh
As an ADMIN you can connect to the schedulix server using sdmsh and enter the command
alter job 60821 with state = finished, exit code = 1;
The job will be finished and CANCELLED.
Regards
Dieter