RE: wrkprb issue

Hi Jerry,

I just did a WRKPRB then Sys Req 3 then option 14. This showed QASXPROB & QASXPROB2 open in QUSRSYS. I then went back to the WRKPRB screen and took option 5 to display details for a problem. I then Sys Req 3 then option 14. This showed a whole heap of QASX* files open in QUSRSYS. Determine how these all relate to each other, use STRSQL with appropriate DELETEs and make sure you have your cowboy boots on :)

Alternatively the DLTPRB command may allow you to delete many problems in one go based on age or status or whatever else is supported.

Alternatively DSPPRB to an outfile and process the outfile in a CL, and DLTPRB each one as you (programmatically) see fit.

These things I found from an IBM i command entry screen only, with a little knowledge of what can be done in a CL program.

Regards,

Kevin "Are these problems or opportunities?" Wright

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jerry Draper
Sent: Thursday, 22 September 2011 10:16 AM
To: Midrange Systems Technical Discussion
Subject: wrkprb issue


We had a fan go out on a system and it spewed out thousands
of messages
to qsysopr msgq (every two minutes) and created problem ID's every
instance so there are thousands of entries in WRKPRB.

It's not reasonable to close every problem ID.

How can these be cleared out programatically?

TIA,

Jerry

--
Jerome Draper, Trilobyte Software Systems
iSeries, Network, and Connectivity Specialists -- iSeries, LAN/WAN/VPN
Representing WinTronix, Synapse, Netopia, HiT, and others .....
(415) 457-3431 . www.trilosoft.com


--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.