Message server cannot start SolMan 7.0 Ehp1 kernel 7.01 rel.32

[Former Member]

Hi

I'm currently installing Solution Manager 7.0 Ehp1 on iseries 6R1.

I'm stuck on starting central services instance:

During ms server startup i'm receiving error:

-

---

trc file: "dev_ms", trc level: 1, release: "701"

-

---

[Thr 1] Fri May 15 13:19:20 2009

[Thr 1] MsSOsPrivInit: Cannot retrieve system value QDYNPTYSCD

[Thr 1] *** ERROR => MsSOsPrivInit: Run priority must be between 20 and 80 (current = -1) [msuxserv_mt. 226]

[Thr 1] *** ERROR => MsSOsPrivInit: Can't set run priority. [msuxserv_mt. 239]

[Thr 1] *** ERROR => Check OS/400 Joblog. [msuxserv_mt. 240]

and in iseries log there is an entry:

File . . . . . : QPJOBLOG Page/Line 1/1

Control . . . . . W35 Columns 35 - 112

Find . . . . . .

....4........5........6........7........8........9........0........1..

Job Log xxxxxx01 05/15/09 13:19:18

CLWRAPPER User . . . . . . : SMB13 Number . . . . . . . . . .

R3_13 Library . . . . . : R3SMB400

SEV DATE TIME FROM PGM LIBRARY INST TO PGM

40 05/15/09 13:19:18.714765 QDMSIGNL QSYS 0078 QC2IO

To module . . . . . . . . . : QC2SMOPN

To procedure . . . . . . . : _C DM open file

Statement . . . . . . . . . : 10

Message . . . . : File QINLINE in library *LIBL not found or inline data

file missing.

Cause . . . . . : The file was not opened. The reason code is 03. The

reason codes and their meanings are as follows: 01 - The library does not

exist. 02 - The file does not exist. The library does exist. 03 - The fi

does not exist. The library specified as *LIBL. 04 - The file was saved

with storage freed. 07 - An inline data file does not exist. 08 - A diske

file with SPOOL(*YES) is being opened for a read operation and an inline

I've found similar thread under:

but no resolution ...

Kernel release 32 7.01

Parameter QDYNPTYSCD has value 1 of course ...

Unfortunetely customer saprouter will be ready next week anyway i'm opening OSS ticket

Do you have idea what might be wrong ? I suspect kernel but ...

[Former Member]

This resolved my issue! Thanks much!

-Diana

[Former Member]

OSS ticket ( 469524 / 2009 )

[tj_wilkinson2]

You can try to give the <sid>ofr and <sid>nn users *allobj to see if it's an authority problem. You might be able to narrow it down from there.

[Former Member]

Unfortunetely not. With *ALLOBJ same behaviour.

[Former Member]

OK to solve this issue please use note 1134777 for nw2004s SP3 and point:

-

---

<C5038284, Mar/09>----

---

IBM i 6.1 & i5/OS V5R4

While installing an SAP system it does not come up when started for the first time.

Symptom:

When your system doesnot come up have a look into the work directory. There should be a file sapstart.log. In this file you will find following entry:

Cannot execute "/usr/sap/<SID>/SYS/exe/run/cleanipc 01 remove" - as4_examine failed.

system(/usr/sap/<SID>/SYS/exe/run/cleanipc 01 remove) failed(-1). 3474 Error 3474 occurred.

3474 means CPE3474 and points to missing permissions for some system objects.

Solution:

Grant missing object authorities:

GRTOBJAUT OBJ(QSYS/QPMLPFRD) OBJTYPE(PGM) USER(R3GROUP) AUT(USE)

GRTOBJAUT OBJ(QSYS/QPMWKCOL) OBJTYPE(PGM) USER(R3GROUP) AUT(USE)

GRTOBJAUT OBJ(QSYS/QP0ZIPCS) OBJTYPE(PGM) USER(R3GROUP) AUT(USE)

GRTOBJAUT OBJ(QSYS/QPMLPMGT) OBJTYPE(SRVPGM) USER(R3GROUP) AUT(USE)

Now there will be no permission problem anymore to start the new SAP system on your new server.