Ansicht
Dokumentation
10181 - SAPOSCOL
General Data in Customer Master CPI1466 during BackupThis documentation is copyright by SAP AG.
SAPOSCOL
Thank you very much David,I had a hunch this was my problem but since it is no longer possible to
download SAPOSCOL from the marketplace I decided to explore other avenues
until the new kernel CD gets here.
I just received the new kernel CD and applied it and now my SAPOSCOL works
perfectly.
Many thanks to everyone who responded,
Erik Huot
South Shore Industries Ltd.
-----Message d'origine-----
De : davidlopezZcaprabo.es [mailto:davidlopezZcaprabo.es]
Envoyé : 14 mai, 2003 03:42
À : DoNotReply@consolut.eu
Objet : RE: SAPOSCOL
Hi Friends.
Time ago we have the same issue, and it was only a release problem, Kernel
patch and Saposcol patch wasn't compatible. We was fighting some days, we
put PTF's too, incidence with IBM and SAP, etc, and finaly it was this
litlle thing. I now it's a typical Support solution jeje, but try to put
the last kernel & saposcol patch.
I hope it can help U.
Best Regards.
David Lópezz
System Admin.
Caprabo S.A.
"Erik Huot"
<ehuotZsouthshore-i Para:
<DoNotReply@consolut.eu>
ndltd.com> cc:
Asunto: RE:
SAPOSCOL
13/05/2003 19:27
Por favor, responda
a SAP on System i
Hi John,
I verified the authorization list R3ADMAUTL as you suggested.
I also Installed the following PTF's (MF29911, SI07302, SI07443, SI07653,
and SI08620).
In addition, I verified the authorization on QPMWKCOL and QPMLPFRD
according
to OSS note 175852 (as suggested by Jean Francois Quinet.)
However SAPOSCOL still says "shared memory not available".
Would you have any additional suggestion?
Regards,
Erik Huot
South Shore Industries Ltd.
-----Message d'origine-----
De : John Dulek [mailto:dulekZus.ibm.com]
Envoye : 13 mai, 2003 11:33
A : DoNotReply@consolut.eu
Objet : RE: SAPOSCOL
Make sure you check the authority problem:
Heres is a possible solution you can try SAP found the problem on the
customer system. The authorization list R3ADMAUTL was not set correctly.
SAP/Customer changed it this way.
1) Removed QSECOFR *ALL X
2) Changed *PUBLIC from *USE to *EXCLUDE
3) Added R3OWNER *ALL X
The SAPOSCOL can now be started normally via transaction ST06.
The SAPOSCOL can also be started by using this command instead
of transaction ST06.
CALL PGM(<kernel lib>/SAPOSCOL PARM('-l')
John Dulek
Staff Software Engineer Rochester Support Center
iSeries 400 SAP/Siebel/SSA/Database
507-286-6697 DULEKZUS.IBM.COM
Bldg 664-2 Room J227 3055 41st St. NW
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Durban Tours - Südafrika Safari
CL_GUI_FRONTEND_SERVICES - Frontend Services Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 5210 Date: 20240520 Time: 190745 sap01-206 ( 2 ms )
