Top
Systemwalker Operation Manager Troubleshooting Guide
FUJITSU Software

4.8.3 Even if the Termination Processing Job Net is Completed, the Server does not Reboot/Shut Down

Applicable versions and levels

Action 1

Points to check

Is the job net name (not the job net comment) "JSHEND"/"JSHFORCE"?

Action method

Even if the job net comment is "JSHEND"/"JSHFORCE", if the job net name is not "JSHEND"/"JSHFORCE", the Completed/Abended shutdown exit will not be called. Make the job net name "JSHEND"/"JSHFORCE".

Action 2

Points to check

Was JSHEND/JSHFORCE created in a project with the project name "SYSTEM"?

Note: In V13.3.1 or earlier, check if a project created with the same name as the user name registered in the Systemwalker MpJobsch service startup account was registered.

Action method

Create JSHEND/JSHFORCE in a project with the project name "SYSTEM".

Action 3

(V13.3.1 or earlier)

Points to check

Is a Windows x86 version Systemwalker Operation Manager running in a Windows 64-bit environment?

Cause

If a Windows x86 version Systemwalker Operation Manager is used in a Windows 64-bit environment, the operating system shutdown command cannot be executed even if it is defined in the shutdown exit. This is because the Windows x86 version Systemwalker Operation Manager is a 32-bit application, so the <system directory>\System32 directory cannot be accessed because of the file system redirection function of the operating system. Refer to the Microsoft Knowledge Base Article 942589 for details.

Action method

Take action according to the Microsoft Knowledge Base Article 942589.