SAPOSCOL not running ? (shared memory not available ) after upgrade to V5R3

[Former Member]

Hi to all,

I have upgraded OS/400 from V5R2 to V5R3 and since that, the SAPOSCOL not running properly.

I get the message "SAPOSCOL not running ? (shared memory not available )".

We run SAP 46 C, Kernel 46D_EXT level 2284. ASCII.

I have done the following:

Implemented note 175852.

Update SAPOSCOL to level 95.

Delete the temporary user space, R3400/ PERFMISC*.

Remove the shared memory coll.put.

End the jobs QPMASERV, QPMACLCT,QYPSPFRCOL,CRTPFRDTA, SAPOSCOL.

Start SAPOSCOL from ST06.

But SAPOSCOL does not run.

Any ideas before open a PRM at IBM, as it is recommended in note 743113 - iSeres: Known Issues with V5R3, If the problem is not solve after applied note 175852.?

Regards

Eduardo Barrios

Compañía Cervecera de Canarias S.A.

Tfno. 922 568 246

Fax. 922 670 600

ebarrios@ccc.es

[Former Member · Accepted solution]

Hi Eduardo,

Have you checked all the IBM infopar II13868 for V5R3 and applied all the necessary PTF's?

If not check it here :

http://www-1.ibm.com/support/docview.wss?uid=nas219661e9da554d52186256e98003c8562

Most probably it is a PTF issue and will be solved by the PTF, as u have already tried note 175852.

I would suggest compare all the PTF's in the infopar first and if all of them are there, then open up a PMR...

Thanks

Abhi

[franco_tassone · Accepted solution]

Hi all,

we had similiar issues in the past, here's how we could solve:

***

First of all you should be aware that kernel and SAPOSCOL are on the

latest level (see SAP Notes: #708136, #753917).

Furthermore kindly check if both programs QPMLPFRD and QPMWKCOL in

library QSYS have *USE- authority assigned for user R3OWNER.

(see SAP Note: #175852).

Otherwise you have to run the following commands:

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

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

Then you should verify if the user R3OWNER is part of authority list

R3ADMAUTL (see SAP Note: #637174).

If everything would be fine but you would get the same error message,

then please do the following steps before trying to start SAPOSCOL

program again:

Kindly remove the shared memory (coll.put)

(according to SAP Note: #189072). You could find 'coll.put' here:

'/usr/sap/tmp'.

Finally please end the following jobs in QSYSWRK (if these ones are

running): QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA

...and delete the temporary user space:

WRKOBJ OBJ(R3400/PERFMISC) OBJTYPE(USRSPC)

also do the followings:

1- ENDTCPSVR *MGTC

2- CALL QYPSENDC PARM('*PFR ' ' ')

*note There are 6 blanks after *PFR and there are 6 blanks making

up the second parameter.

3- ENDJOB JOB(xxxxxx/QSYS/QYPSPFRCOL) OPTION(IMMED) SPLFILE(YES)

*note This command must be run for all QYPSPFRCOL jobs found on

the system even if they show with *OUTQ as their status.

4- ENDJOB JOB(xxxxxx/QSYS/CRTPFRDTA) OPTION(IMMED) SPLFILE(YES)

*note This command must be run for all CRTPFRDTA jobs even if

they show with *OUTQ as their status.

5- RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*USRSPC) NEWOBJ(QPFRCOLDTX)

6- RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*DTAQ) NEWOBJ(QPFRCOLDTX)

*note This object may or may not exist at this time.

7- CALL QYPSCOLDTA

*note This program will create a new *USRSPC. After collection

services is started there should be a new *DTAQ.

8- Start collection services using GO PERFORM, opt 2, and opt 1;

OR

CALL QYPSSTRC PARM('PFR ' 'STANDARDP' ' ')

*note There are 6 blanks after *PFR and there are 6 blanks

making up the third parameter.

OR

Start collection services from Operations Navigator.

9- STRTCPSVR *MGTC

10- End and restart Operations Navigator if it is being used.

See IBM apar SE12188 for more infos.

Try restarting SAPOSCOL from ST06 now: this procedure normally works for us.

Kind regards.

Franco Tassone

[Former Member]

Hi Christian, and thanks again.

The program is not installed. I have requested to IBM the PTF,s in APAR II13868.

Regards

Eduardo

[christian_bartels]

If the OS collector is hanging for 10 minutes or more, you should double-check if PTF SI26590 (for V5R3) is installed. This PTF fixes a problem where the OS collector remained in DEQW forever after the start. The equivalent PTF in V5R4 is SI26585.

If the PTF is installed and the problem is still not solved, you should report it to SAP or IBM for in-depth analysis.

Kind regards,

Christian Bartels.

[Former Member]

Hi Christian,

I have started SAPOSCOL manually and the screen input was inhibited without messages. After 10 minutes, I canceled the job.

In usr/sap/tmp/dev_coll there is no new entries for today. The last entries was registered on 05.04.2007 before I start the upgrade to V5R3.

There is entries for today in dev_coll.tmp

08:35:01 18.04.2007 MSG: ====================================================================================

08:35:01 18.04.2007 MSG: = OS Collector Start

08:35:01 18.04.2007 MSG: ====================================================================================

08:35:01 18.04.2007 MSG: Starting R346DAOPT/SAPOSCOL

08:35:01 18.04.2007 MSG: Saposcol Version is [COLL 20.79 03/08/22 46D - AS/400 SAPOSCOL Version (ILE/ASCII) 22 Feb 2006

Regards

Eduardo

[christian_bartels]

My suggestion would be to try collecting more information about the cause of the problem:

1. Signon as <sid>OFR and start SAPOSCOL manually by using the command CALL PGM(SAPOSCOL) PARM('-l'). After that, screen input may be inhibited for about a minute, because SAPOSCOL waits for some initial data to be collected. Eventually you should get a message "Starting collector (create new process)". If not, it would be nice to know what else you get. Starting the collector manually works, we need to find out why ST06 does not work.

2. Check the contents of /usr/sap/tmp/dev_coll. Maybe this contains more information where the problem is.

Kind regars,

Christian Bartels.

[Former Member]

Hi Brian,

I have tried your recommendations, but the issue remains.

Thanks for your help.

Regards

Eduardo

[Former Member]

Thanks to all for your help.

I have set the Franco`s recommendations, but the issue still appear.

I have opened a PMR at IBM, and they recommend me to apply the required PTF,s in infoapar II13868.

I have checked the II13868 and there are some missing PTF,s.

Regards

Eduardo Barrios

[blaw]

We have had problems with the SAPOSCOL -

You can try

1) Stop your SAP system and four relevant jobs in QSYSWRK - QYPSPFRCOL, QPMACLCT, QPMASERV and CRTPRFDTA

2) Clear the Collector Memory Segment with following command:

Call <kernel>/cleanipc parm('99' remove')

3) Start your SAP system again - Saposcol should start automatically and ST06 should show data.

Regards,

Brian

[Former Member]

There is no alternative you have to follow the note 743113 point 7. if not then open PMR at IBM.

Cheers,

-Sunil