SAP Basis

ADM100 Lesson: Appendix - Troubleshooting Example
5. Identify the spool work process that generated the output request. To
do this, investigate the spool work processes of the instance that you
identified in the previous task.
a) To do this, you can search all developer traces of the spool
work processes of the SAP applications server identified in
the previous task. Alternatively, open a Command Prompt at
operating system level in the work directory of the instance. You
can search the trace file with the command qgrep here. If the
front end printer has the short name TFRP, the call is: qgrep -l
-e TFRP dev_* . All trace files in which TFRP (case-sensitive)
appears are displayed. The name of the developer trace in which
the text was found is displayed at the start of each line. View
only the trace files associated with a spool work process. You
cancheckthetracefilesfromtheoperatingsystemorfrom
transaction SM50 . In the dialog work process trace file, you find,
in Printer Trace, the lineS sending frontend job
xxxx/y, among other things. xxxx specifies the spool number
and y the output request number. You can use this information
to ensure that you are analyzing the trace information for your
output request.
6. Check whether SAPLPD was started in the spool work process trace.
a) In the spool work process trace, searchforthelocationwiththe
TCP_OPEN entries. Ensure (as in the previous steps) that you are
analyzing the trace information for the output request.
For the first TCP_OPEN, you find the return value retcode =
2. This means that SAPLPD was not started. It is now started
in the line TCP_START. The return value for this is retcode
= 0. This means that SAPLPD was started. The subsequent
TCP_OPEN call is now also successful with retcode = 0.
Continued on next page
2003/Q3 © 2003 SAP AG. All rights reserved. 575