Delay between the SHUTDOWN and SHUTDOWN IMMEDIATE commands

[Alain Roberge]

Hello,
When the SHUTDOWN command is received by IDMS, our OPS team allows 15 minutes for IDMS to complete. Beyond this delay, OPS issues a SHUTDOWN IMMEDIATE command to cancel ongoing tasks and allow IDMS to terminate. This process works well. The 15-minute interval between the two commands was established several decades ago.

Can I reduce the waiting time between the SHUTDOWN and SHUTDOWN IMMEDIATE commands, which is currently 15 minutes? In 2025, what would be an acceptable delay?

Thank you 

Alain

[Tom Hebert (IUA)]

Alain,

This approach is easy for the operators, and probably a straightforward automation setup task. It's been working for you for many years and may work for others as well. There are additional things to consider.

Here's a teaser. The IUA is Rebooting! Your topic would be a good one for our soon-to-be best practices repository on GitHub. No kidding. The IUA is coming GitHub, and more!

We are finalizing our presentation for the Virtual MTE and working to implement and reveal a new set of IUA community offerings at the in-person MTE this fall! Sign up for the Virtual MTE, look up our session and put it on your schedule. It'll be worth your time.

Don't just sign up. This is a must-see presentation for everyone whose careers are affected by IDMS. Start connecting with other DBAs, programmers, software engineers, managers, system architects, directors, or officers at your company, and your client companies. They need to see this too.

So Alain, consider this an invitation to be one of the IUA's first Best Practice Contributors. We're ready to work with you, and anyone else who is ready to share their expertise! And we're looking for additional topics!

Here is the name of the presentation: DBM02: Partnering with You: IDMS User Association Community Update

------------------------------
Tom Hebert
President IUA
ObjEx Cofounder
------------------------------

[Wesley Atkinson]

It really depends on your environment.  Have you done a DRU command to see what is active in the system? If it's production batch, you may or may not want those jobs to be forced out.  Once you get a feel for what's causing shutdown to not complete it will be easier to decide if and how quickly to issue the shutdown immediate.