You can monitor the performance of your SAP spool system in the context of the SAP monitoring architecture. The Spool Monitor provides you with a tool with which you can obtain an overview of the system status quickly and can react to alert messages.
The monitoring architecture of the SAP System provides you with various options for monitoring your system and analyzing any errors.
Activities
Start the Spool Monitor by calling transaction RZ20 (or choosing Tools ® CCMS ® Control/Monitoring ® Alert Monitor). ON the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates monitor set, and start the Spool System monitor by double clicking it. The system displays a monitoring tree you can expand to display the information you require.
You can use this monitor template as is, or you can copy it into your own monitor set and modify it.
Features
The spool monitoring tree consists of the subtrees System Wide and Spool Servers. The table below explains the individual components (Monitoring Tree Elements,MTEs) of the subtrees. Threshold values are set for the individual attributes. Each attribute has a color indicating whether the current attribute value falls below or exceeds the threshold value. For information about the meaning of the colors and symbols, see Extras ® Legend. The tree can display the attributes from several points of view. You can select the view level by choosing Extras ® Display options and then Dsply tree.
System Wide Subtree
The System Wide subtree contains information about the current utilization of the number range for the spool numbers and wait times and status attributes for the individual spool services of the system.
The subtree contains the following monitoring tree elements (Monitoring Tree Elements = MTEs):
| MTE | Meaning |
| SpoolNumbers | Spool number that is assigned to every output request |
| UsedNumbers | Usage of the spool numbers as a percentage; you must delete old output requests before this number reaches 100 percent |
| Status | Is only displayed if the spool service is associated with an SAP application server |
| WaitTime | Wait time in the spool service in seconds |
Spool Servers Subtree
The Spool Servers subtree contains monitoring objects about the spool system, broken down by application server, where subtrees are generated only for the servers with at least one spool work process:
Entries in the System Log (R3Syslog) Connected with the Spool System
The R3Syslog log attribute displays system log messages on the spool category; you set the message text, the category and the severity and criticality of the alert using the message ID in transaction SE92.
SpoolService
The SpoolService monitoring object contains the most important attributes about the spool system, its usage, and the length of the wait queues. It includes the following MTEs:
| MTE | Meaning | Comments |
| Utilization | Usage of the spool work processes as a percentage |
|
| NumberOfWpSPO | Number of spool work processes | You set the number of these Workprozesse using system parameter rdisp/wp_no_spo (For recommendations, see SAP Note 108799). |
| QueueLength | Used area of the dispatcher queue as a percentage | Output requests are buffered in the dispatcher queue on the spool server until a free work process accepts them. |
| ServiceQueue | Used area of the spool request queue as a percentage | The spool request queue accepts output requests from the dispatcher queue if a free work process in the spool server accepts the output request. |
| ServiceQueuePriv | Used area of the spool request queue for chronological processing as a percentage | If a spool server has multiple spool work processes, the output requests can overtake each other. To retain the sequence of the requests, theere are special work process-specific output queues, each with requests for a specific output device. |
| ServiceQueuePages | Number of pages in the spool request queue |
|
| DeviceCacheUsed | Used area of the entire device cache as a percentage | The device cache contains device definitions and server assignments for all work proceses. Entries are read into the cache as required, and can be replaced again if the cache becomes full. |
| DeviceCacheFixed | Used area of the fixed device cache as a percentage | This area contains information about the output devices for which requests exist in the host spool system and that have not yet been reported as finished. The cache must therefore contain as many entries as the maximum number of devices that can be used simultaneously. |
| HostspoolListUsed | Used area of the spool request queue as a percentage | The host spool request list limits the number of requests in the host spool that can be managed by the spool service. To minimize database accesses, the list must be held in shared memory. It serves as a status query for the current requests. |
For more information about this topic, see the SAP Service Marketplace under SAP Note 118057 (Flexible Configuration of the Spool-Service).
Processing Groups
We recommend that you assign both the spool servers and the output devices to various classes for the classification of output requests. By using different spool servers that process requests of different types (and priorities), you can prevent, or at least control, output requests blocking each other. The Processing Groups node contains the following processing groups:
| MTE | Meaning | Comments |
| ProcessingGroup Adm | Spool administration tasks | Examples: · Activating delayed requests · Deleting obsolete requests · Diverting requests if a server fails |
| ProcessingGroup Reg | Normal requests | Normal requests are requests to devices that are assigned to a spool server. |
| ProcessingGroup Fro | Requests for frontend output devices | Define frontend output devices at operating system level. An output device that sends output requests to the user’s default printer must exist in the SAP R/3 System with the access method F (frontend). |
| ProcessingGroup Vol | Requests classified as mass printing | Mass printing means very large requests. Assign these requests to a separate spool server to avoid blocking other output requests. |
| ProcessingGroup Pro | Requests classified as production printing | Production printing should include the output requests required for smooth production operation (such as invoices). We recommend that you connect output devices of this processing group locally. |
| ProcessingGroup Dsk | Requests classified as desktop printing | Desktop printing should include printers at work stations. As they are often not available, they can block other requests. We recommend that you do not use this processing group for output requests that are important for running the business of your company. |
| ProcessingGroup Tst | Requests classified as test printing | Test printing should include those output devices that are used to test new device types or configurations. |
The monitor contains the following MTEs for each of the processing groups:
| MTE | Meaning |
| GroupWPs | Number of work processes |
| GroupJobs | Number of requests |
| GroupPages | Number of pages |
| GroupMinWPs | Reservation of work processes |
| GroupMaxWPs | Restriction of the number of work processes |
Note with reservation of work processes (GroupMinWPs), that these can remain unused, even if there is no request for this group, the other work processes are occupied, and other requests for other groups are waiting to be processed. In the same way, a restriction of the number of work processes (GroupMaxWPs) means that even if there are other requests waiting to be processed in this group and other work processes are unoccupied, the number of work processes for this group cannot be increased.
Output Devices (Devices)
You can also use the monitoring architecture to monitor specific output devices that are especially important for the smooth production operation. You can do this in Spool Administration (transaction SPAD) by seleclting the Monitor using monitoring architecture indicator on the Output Attributes tab page of an output device (see also Output Devices in the SAP Spool System). If you have activated this monitoring for at least one device, there are monitoring objects in the Devices subtree with the short name of the output device and the following MTEs:
| MTE | Meaning |
| LPQ_Time | Time an output request spends in the output device queue |
| Pages/Min. | Print speed in pages per minute |
| Message | Status attribute that displays any errors that occur during the transfer of the output request to the host spool system |
No comments:
Post a Comment