Shared Memory Areas

1 "System administration "

2 "Disp. administration tables "

3 "Disp. communication areas "

4 "statistic area "

5 "SCSA area "

6 "ABAP program buffer "

7 "Update task administration "

8 "Paging buffer "

9 "Roll buffer "

10 "Pool "

11 "Factory calender buffer "

12 "TemSe Char-Code convert Buf. "

13 "Alert Area "

14 "Presentation buffer "

15 "Document administration "

16 "Semaphore activity monitoring"

17 "Roll administration "

18 "Paging adminitration "

19 "Table-buffer "

20 "Unused1 "

21 "Unused2 "

22 "Unused3 "

23 "Unused4 "

24 "Unused5 "

25 "Unused6 "

26 "Unused7 "

27 "Unused8 "

28 "Unused9 "

29 "Unused10 "

30 "Taskhandler runtime admin. "

31 "Dispatcher request queue "

32 "unknown segment "

33 "Table buffer, part.buffering "

34 "Enqueue table "

35 "Sap-Communication BK/EDI "

36 "Performance monitoring "

37 "Fast SEM ADM on MPE & AS400 "

38 "Event ADM on AS400 "

39 "Queue ADM on AS400 "

40 "Pool for database buffers "

41 "DB statistics buffer "

42 "DB TTAB buffer "

43 "DB FTAB buffer "

44 "DB IREC buffer "

45 "DB short nametab buffer "

46 "DB sync table "

47 "DB CUA buffer "

48 "Number range buffer "

49 "Spool admin (SpoolWP+DiaWP) "

50 "Pool 50 "

51 "Extended memory admin. "

52 "Message Server buffer "

53 "Extended memory test tool "

54 "Export/Import buffer "

55 "Spool local printer+joblist "

56 "Application statistics "

57 "Profilparameter in shared mem"

58 "Enqueue ID for reset "

59 "Enqueue table extension AS400"

60 "Enqueue table addition AS400"

61 "Extended memory only on AS400"

62 "Memory pipes "

63 "ICMAN shared memory "

64 "Online Text Repository Buf. "

65 "Export/Import Shared Memory "

66 "Enqueue Replication Shadow "

67 "ICRouter HTTP Client Table "

68 "JControl Administration "

69 "JControl Administration "

70 "java area "

71 "ITS Events "

72 "ITS Mutexe "

73 "CCMS Extended Alert Area "

74 "VMC Lite Admin "

75 "VMC Lite ES "

76 "Ext. Segment Administration "

77 "Ext. Memory Administration "

78 "Ext. Global Memory Admin "

79 "JStart static instance info "

80 "JStart dynamic data "

81 "Security Audit Log "

82 "Web Disp EUID Table "

83 "ABAP Coverage Analyzer "

101 "Performance monitoring "

102 "Performance monitoring V01.0 "

103 "Global spool storage "

108 "Network monitoring "

121 "SCSA area "

sappfpar

Some hits from sappfpar:

1. to list all instance parameters

sappfpar all pf="INSTANCE PROFILE"

2. to check the memory parameter in the instance and check the recognized parameters

sappfpar check pf="INSTANCE PROFILE"

Memory pipes (MPI)

The ICM require two memory pipes (MPI) for each HTTP connection.

The MPI configuration in the ICM is limited by parameter

mpi/max_pipes. The default value for this paramter is 4000.

If you has 4000 for that parameter the operation system should provide 8000 operating system semaphores because eatch MPI require two semaphores.

To increase the parameter mpi/max_pipes you should take care the operation system configuration also. Follow the note 715400 to set the operation system as you need.

715400 Max. number of memory pipes (MPI) restricted to 4,000

ERROR MESSAGE:

ERROR => no more free event-flags. [mpixx_mt.c 4555]

ERROR => MpiEvtOpen(0) failed: 11 [mpix_mt.c 1169]

ERROR => IcmConnInitBuffer: MpiCreate2 failed (rc=11)

means that no more semaphores can be created because the ICM reach the

Operation System limits.

HTTPWatch traces

1. Install the free version of HTTPWatch 6.x (http://www.httpwatch.com)

on your Internet Explorer.

2. Start the browser, start the HTTPWatch, click on 'Record' button,

and please reproduce the issue.

3. On finish 'Save' the contents of HTTPWatch as a .hwl file

(Please note: Exporting as CSV or XML is not so helpful, so please use

the default save option).

4. Save .hwl file to this message.

Logon-Check Availability

Function module responsible: SCSM_RUN_RFC_LOGON_CHECK

All ABAP instance with the 'Logon-Check' is set in the CCMSPING availability configuration

will be monitored by the agent.

The SCSM_RUN_RFC_LOGON_CHECK will do this by creating an ARFC session

for each instance and it will wait for an answers of each of these ARFC.

If you have the note 929577, the sessions time out will be by default 2 seconds. If the note is not implementdthe timeout is determined by RFCPING_TIMEOUT.

Trace file's rotation and system restart

You have lost the trace file to perform an anlysis on the system behavior after an error/crash/hung situation.

Every system restart, the trace files are overwritten.
When you start the instance, all files from the services (message
server, dispatcher, work process, ICM and others) are truncated and only
the actual log status information are writen.

But, before truncate the actual trace files, the system create a backup
of this trace file with the .old extension.

Although exist the mechanism to create a backup of the trace file, if
you restart the system more than one time, the .old trace file will be
overwritten too.

A good pratice is make a copy of the work directory before the start up.

Parameter changes without restart

If you need to change some memory parameters but you cannot restart the instance, have solution.
You can change the parameters from RZ11 and run the remport RSMEMORY.

610965 Parameter in RZ11 cannot be switched