topic Re: safecom problem in Operating System - NonStop OS

safecom problem

TomaszSerwanski — Wed, 10 Jun 2015 12:48:57 GMT

Hello,

Trying to add new user; as result I see:

=====

=delete user kurs.user1
* ERROR * CANNOT OPEN $ZSMP : FILE ERROR = 201

=====

process $zsmp in fact does not exist; could anybody advice what could be the reason:

- $zsmp disappeared

- how to restart it?

regards

Tomasz

Re: safecom problem

Paul Kurtz — Wed, 10 Jun 2015 18:37:03 GMT

From Tacl you need to run SCF and assume $zzkrn and then run status process $ZZKRN.#* and see if #ZSMP is running.

IF not you can run start process $zzkrn.#ZSMP from SCF.

Make sure you are super.super

Re: safecom problem

TomaszSerwanski — Thu, 11 Jun 2015 08:23:22 GMT

Hello Paul,

Thank you for your answer; I did what you suggested, problem is that $ZSMP was in started status for a while, and got back to stopped:

======

3-> start process $zzkrn.#ZSMP
KERNEL W00030 Process \PKP.$ZSMP started successfully.
4-> status process $ZZKRN.#ZSMP

NONSTOP KERNEL - Status PROCESS \PKP.$ZZKRN.#ZSMP

Symbolic Name Name State Sub Primary Backup Owner
PID PID ID
ZSMP $ZSMP STARTED 0 ,1167 None 255,255
5-> status process $ZZKRN.#ZSMP

NONSTOP KERNEL - Status PROCESS \PKP.$ZZKRN.#ZSMP

Symbolic Name Name State Sub Primary Backup Owner
PID PID ID
ZSMP $ZSMP STARTED 0 ,1167 None 255,255
6-> status process $ZZKRN.#ZSMP

NONSTOP KERNEL - Status PROCESS \PKP.$ZZKRN.#ZSMP

Symbolic Name Name State Sub Primary Backup Owner
PID PID ID
ZSMP $ZSMP STOPPED None None
7->

======

I've opened case to HP already, but maybe you are aware what may be the problem?

regards

Tomasz

Re: safecom problem

barkath — Wed, 17 Jun 2015 02:12:23 GMT

Hi Tomasz,

Error 201 indicates that path to the device is down. Can you please check the EMS logs while starting the $ZSMP process and see you get any clues.

0201 The current path to the device is down, an attempt was made to write to a
non-existent process, the message-system request was incorrectly
formatted, or an error was found in the message system interface.

Re: safecom problem

TomaszSerwanski — Tue, 23 Jun 2015 10:37:00 GMT

Hello,

Seems root cause was entry in config; 'startup message' entry was as abowe:

*StartupMessage............Starting process $ZSMP

While fixed is:

*StartupMessage............"<BCKP-CPU>"

At the moment it works fine.

regards

Tomasz