You are searching about What Is S P-F A As F.O.B Code, today we will share with you article about What Is S P-F A As F.O.B Code was compiled and edited by our team from many sources on the internet. Hope this article on the topic What Is S P-F A As F.O.B Code is useful to you.
The SAP System OS Collector – SAPOSCOL in a Nutshell
The SAP System OS collector (SAPOSCOL) is a platform-independent, stand-alone program that runs in the background of the operating system and uses a segment of shared memory to collect system information for various applications and all SAP instances on the host. This information can be viewed in the frontend SAPGUI via transaction code ST06/OS06. This is a very useful tool for NetWeaver/Basis administrators and consultants to monitor server performance. SAPOSCOL extracts real-time data from the system, although it is not updated automatically, the Update button must be clicked to display the updated data. SAPOSCOL collects and records system data every 10 seconds and records hourly averages for the past 24 hours. It autonomously runs exactly one process per host from SAP instances and collects data from various operating system resources. A user can manage all SAP servers with this tool. But in the case of a remote server (livecache server), the transaction code is OS07. From the monitoring list, you can check CPU utilization, physical and virtual memory usage, pool data/swap sizes, disk response time, physical disk and file system utilization, resource load of running processes, and even LAN data.
You can navigate to this tool from SAP menu->Tools->CCMS->Control/Monitoring->Performance->Operating System->Local->Activity.
If you don’t see any data, it means that the OS Collector (SAPOSCOL) is not running (error code: Shared memory not available). In this situation, its main task is to fix the saposcol to work properly. This usually happens after a new SAP installation or kernel update. If you are new to SAP Systems, the following guide will be helpful in solving your saposcol issue.
First check the saposcol.exe file permission, it should be 777 (owner is root in sapsys group) and sticky bit should be set to 4750. To find out which user is running saposcol, use “ps -ef | grep”. saposcol”. Now to change the saposcol file to owner root, group sapsys, mode 4750, login as root user in unix system and execute below commands,
chown root saposcol
chgrp sapsys saposcol
chmod 4750 saposcol
You can also run the “saproot.sh” file in the exe directory to set the permissions. Then run saposcol as the same owner (root). Check the status of the collector with saposcol -s. After setting file permissions, you can also use ST06 -> Operating System Collector -> Click ‘Start’ to run SAPOSCOL.
Use the saposcol -k command to stop the OS collector. If this command failed to stop the process, you can execute the “cleanipc 99 remove” command (Check SAP Note 548699). If this attempt also fails, you need to remove the saposcol shared memory key. Run the command “ipcs -ma” and note the shared memory ID in the line containing the saposcol key. Then execute the command “ipcrm -m ID”. The shared memory key will be recreated the next time saposcol is run.
Sometimes using “saposcol -l” indicates that it is already running, but greping the process using “ps -ef|grep -i saposcol” may not show the process. In this situation, you can use an undocumented parameter “saposcol -f”, where “f” stands for force-starting the process. When it starts, stop the process in control methon using “saposcol -k” and then start it normally using “saposcol -l”.
If saposcol still does not run, it must be started in dialog mode. Login using adm and follow below steps,
Collector > clear
Collector > exits
to stop the saposcol -ka collector.
Collector > exit (You should get a message – Shared memory deleted)
Collector > exits
mv coll.put coll.put.acid
“coll.put” if this file contains the old shared memory and should be deleted for a clean start (Check SAP Note 548699, point 7). If you fail to clear the shared memory, try the following commands to clear the shared memory:
$ saposcol -kc
$ saposcol -f
If that doesn’t work either, you need to restart the system from the operating system level, and it looks like you also need a new version of saposcol (Check SAP Note 19227).
IBM iSeries i5/OS (OS/400, OS/390):
– Check the permissions of the directory ‘/usr/sap/tmp’ and the file ‘saposcol.exe’, it should be 4755 and the owner should be root in the sapsys group. Check SAP note 790639. After assigning the permissions, you can run it from the command line of the operating system with the command “SAPOSCOL -l”. Use ‘SAPOSCOL -s’ to display the status and ‘SAPOSCOL -k’ to stop the process. You can also run the process by sending an OS-level task using it
CALL PGM(SAPOSCOL) PARM(-l).
The job is submitted in the QBATCH job queue of the QGPL library.
– On iSeries you may experience strange data when analyzing CPU utilization using ST06/OS06 tcode. Even if you use multiple CPUs, SAPOSCOL may only report the CPU usage of the first CPU. Sometimes you may find CPU utilization above 100% at certain intervals if you run the SAP instance on an uncapped partition where multiple logical partitions use a shared processor pool. In this situation, make sure that the CPU usage reported for CPU 0 is the average usage of all CPUs used in the system. If you want to view the data of the shared CPU partitions, apply SAP No. 994025. support packages as noted, including the following patch levels
6.40 disp+work package (DW): 182 SAPOSCOL: 69
7.00 disp+work package (DW): 109 SAPOSCOL: 34
When you apply these fixes and support packs to your system, new transactions OS06N, ST06N, and OS07N are available to view additional information in the “Host System” and “Virtual System” sections. These include information about the partition type and the available and used CPU in the current partition and the shared processor pool. So if you are an iSeries user and SAPOSCOL is not running, you most likely need to install the latest kernel and saposcol patch. (SAP Notes 708136 and 753917)
– Another scenario in iSeries where saposcol does not run and cannot be started from ST06/OS06. The problem may be that the allow list for R3ADMAUTL was not accurate. You can solve it like this,
1) Remove QSECOFR *ALL X
2) Change *PUBLIC from *USE to *EXCLUDE
3) Add R3OWNER *ALL X
Now you can start saposcol using ST06/OS06 tcode. And you can also start the process from the command line,
CALL PGM(/SAPOSCOL PARM(‘-l’).
If this does not solve the problem, check that both programs QPMLPFRD and QPMWKCOL in directory QSYS have *USE authority for user R3OWNER (SAP Note: 175852). If not, you need 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 check if the user R3OWNER is part of the R3ADMAUTL authorization list (SAP Note: 637174). If after that the “SAPOSCOL is not running? (Unable to access shared memory)” error message, follow the steps below,
1) Remove shared memory (coll.put) as per SAP Note: 189072. Location of ‘coll.put’ is ‘/usr/sap/tmp’.
2) End jobs QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA in QSYSWRK if running.
3) Clear the temporary user area, WRKOBJ OBJ(R3400/PERFMISC*) OBJTYPE(*USRSPC)
4) ENDTCPSVR *MGTC
5) CALL QYPSENDC PARM(‘*PFR’ ‘ ‘). [There are 6 blanks after *PFR and there are 6 blanks making up the second parameter]
6) ENDJOB JOB(xxxxxx/QSYS/QYPSPFRCOL) OPTION(*IMMED) SPLFILE(*YES) [This command must be run for all QYPSPFRCOL jobs found on the system even if they show with *OUTQ as their status]
7) ENDJOB JOB(xxxxxx/QSYS/CRTPRDTA) OPTION(*IMMED) SPLFILE(*YES) [This command must be run for all CRTPFRDTA jobs even if they show with *OUTQ as their status]
8) RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*USRSPC) NEWOBJ(QPFRCOLDTX)
9) RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*DTAQ) NEWOBJ(QPFRCOLDTX) [This object may or may not exist at this time]
10) CALL QYPSCOLDTA *note This program creates a new *USRSPC. There must be a new *DTAQ after collection services are started.
11) Start recovery services using GO PERFORM, option 2 and option 1; OR CALL QYPSSTRC PARM(‘*PFR ‘ ‘*STANDARDP’ ‘ ‘) [There are 6 blanks after *PFR and there are 6 blanks making up the second parameter]. Or Start collection services from the Actions navigator.
12) STRTCPSVR *MGTC
13) Close and restart Actions Navigator if it is running. For more information, see IBM Official Program Analysis Report (APAR) SE12188.
14) Now start SAPOSCOL from ST06/OS06.
– Open the Kernel folder in the command line where you will find the saposcol.exe file. Set full ownership permission
to the file and folder. Then run saposcol -l (in the saposcol -d dialog)
– You can also try starting/stopping the SAPOSCOL service from the menu item Control Panel -> Administrative tools -> Services (services.msc).
If all else fails, make sure you are using the correct version of SAPOSCOL. Get the latest SAPOSCOL for your operating system from the SAP Service Marketplace. Download the SAPOSCOL.SAR file for the kernel and save it in a directory. Then STOP SAP & SAPOSCOL. Check your kernel library locks and don’t forget to backup your library. Then run APYR3FIX and then APYSAP. Check OSS Note 19466.
SAPOSCOL can also be terminated due to the small amount of internal memory allocation. When this memory gradually fills up during SAPOSCOL runtime, the system writes the data out of the buffer. As a result, the next buffer is cleared and SAPOSCOL terminates with a dump. Apply the following patches with at least the patch levels specified below:
SAP Release 640: SAPOSCOL patch level 100 and DW 293
SAP Release 700: SAPOSCOL fix level 75 and DW fix level 151
SAP Release 701: SAPOSCOL Patch Level 18 and ILE Patch Level 53
SAP release 710: SAPOSCOL patch level 36 and ILE patch level 161
SAP Release 711: SAPOSCOL Patch Level 12 and ILE Patch Level 48
So it is clear that if we use different SAP systems on one server with an incompatible mix of kernel versions, SAPOSCOL will go into crisis and will not provide data for all systems, even though the SAP system functions run without problems. This is because we are using new IBM technology with EXT kernels, so it does not allow SAPOSCOL to reside in Single Level Storage (SLS) instead of Teraspace. In this situation, it is obvious that if you run an EXT system with another non-EXT system, saposcol will only run on one system. To resolve this issue, you must upgrade to the EXT kernel for all SAP systems with the latest fixes. Then set the appropriate authorization for the SAPOSCOL file and directory according to the guide that will solve the problems with the SAP OS Collector.
Video about What Is S P-F A As F.O.B Code
You can see more content about What Is S P-F A As F.O.B Code on our youtube channel: Click Here
Question about What Is S P-F A As F.O.B Code
If you have any questions about What Is S P-F A As F.O.B Code, please let us know, all your questions or suggestions will help us improve in the following articles!
The article What Is S P-F A As F.O.B Code was compiled by me and my team from many sources. If you find the article What Is S P-F A As F.O.B Code helpful to you, please support the team Like or Share!
Rate Articles What Is S P-F A As F.O.B Code
Rate: 4-5 stars
Search keywords What Is S P-F A As F.O.B Code
What Is S P-F A As F.O.B Code
way What Is S P-F A As F.O.B Code
tutorial What Is S P-F A As F.O.B Code
What Is S P-F A As F.O.B Code free
#SAP #System #Collector #SAPOSCOL #Nutshell