|
|
|
|
|
CMEM receives control for processing events under the various tasks in the system, that is, CMEM acts as part of the address space that issued the corresponding message, command, or other event. For that reason, some of the code and data that are in use by CMEM reside in common storage, accessible from all address spaces, as outlined below. Most of this common storage is above the 16MB line, in the ECSA, but a small portion is allocated by CMEM below the 16MB line, in the CSA, due to MVS services requirements.
Use the information in the following tables to calculate CMEM ECSA and CSA storage requirements:
Table 109 CMEM’s Usage of ECSA Storage Above the 16 MB Line
Item |
Size |
Comments |
|---|---|---|
Subsystem executor |
250 K |
|
Work Buffers |
480 K |
The CMEM monitor allocates 20 work buffers of 24K each, in internal control blocks called WSCs. |
Rules |
50 K |
This amount assumes 500 rules and an average of 100 bytes per rule. |
XES Preallocated Buffers |
3000 K |
Preallocated buffers for XES operations. |
Total |
3780 K |
|
Table 110 CMEM’s Usage of CSA Storage Below the 16 MB Line
Item |
Size |
|---|---|
SWT and other system control blocks |
5.0 K |
Dataset triggering executor |
50.0 K |
UNIX for z/OS interface (USS) |
4.0 K |
Total |
59.0 K |
Parent Topic |