Ansicht
Dokumentation

12301 - Outqs Not being Deleted

12301 - Outqs Not being Deleted

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Outqs Not being Deleted

Hi Phil,

these OUTQs are necessary during the command in order to capture the
output and the joblog. They should normally become deleted
automatically. You could write a small CL-Program, that does a
DSPOBJD OUTQ* *OUTQ => outfile and then a RCVF and issue a CLROUTQ
and then a DLTOUTQ afterwards.

You might want to update your kernel and the SAPXPG to the latest
patchlevel. If this problem still persists, you should open an OSS
ticket.

Regards

Volker

--- In DoNotReply@consolut.eu, "stracenerp" <stracenerpZy...>
wrote:
> Hi All,
>
> We have an abap that uses and external command from SM49 that does
a
> wrksyssts reading in the CPU statistics every 5min. We then use a
> query to analyze the results. I've noticed that in the R3400
library
> there are over 50,000 outqs like OUTQ1xxxxx being created with one
> file in them - the screen shot of the wrksyssts external command
from
> SM49.
>
> Does anyone have insight as to why these outqs are created and why
> they aren't being deleted?
>
> Any ideas on how to get rid of them? I could do a dltoutq with a
> wildcard but each outq has a file in it so it won't let me delete
> it. I would have to clear each outq then delete the outq which is
a
> lot for 50,000+ outqs.
>
> Thanks,
>
> Philip Stracener, CV Industries


Durban Tours - Südafrika Safari

BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.

Length: 1999 Date: 20240329 Time: 161438     sap01-206 ( 4 ms )