set process/suspend

[JKrucus]

I have batch jobs that run for several days, and occasionally I need to reboot, which kills all batch jobs of course.
If I /suspend the batch process before rebooting, can I /resume it after the reboot and have it run like nothing happened?
I assume /suspend /resume works fine on a running system; has anyone tried it with a reboot in the middle?

[Uwe Zessin · Accepted solution]

It will only 'block' the process and prevent any further execution. Unfortunately, on a system shutdown ALL processes are deleted. Last time I checked, OpenVMS cannot preserve a process state that survives a reboot.

You can check the batch "restart" feature, but that is only helpful if you have multiple .EXE files with some DCL code in-between, because the batch "checkpoints" are DCL labels. You still need to cope with the deletion of processes and data inconsistencies due to the deletion.

[Jan van den Ende]

JKrucus,

"I have batch jobs that run for several DAHS" (capitals by me)

and

"occasionally I need to reboot, which kills all batch jobs of course."

It strikes me as strange that you have to reboot VMS DURING a run of ony a few DAYS.

Are you sure you NEED that frequent reboots?

VMS systems routinely run uninterupted for months or years.

I would have a serious review of the NEED for those reboots.

Proost.

Have one on me.

jpe

[Jan van den Ende]

oops.

"DAHS" should read "DAYS"

Proost.

Have one on me.

jpe

[JKrucus]

It is an application issue, not a VMS issue, that requires a reboot, but that is another story.....

[JKrucus]

Thank you, it is as I expected.

[JKrucus]

.

[Lawrence Czlapinski]

Still you should be able to kill the application without having to reboot through Availability Manager if no other way.
Lawrence

[Uwe Zessin]

Re-read the thread: it's not about killing a process!
It's about preserving a process state over reboots.