× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello Rob,

Am 29.05.2020 um 23:21 schrieb Rob Berendt <rob@xxxxxxxxx>:

GO CMDPRB
Do a DSPPRB to an outfile. Process the outfile with the following?
Use DLTPRB. IDK if you have to precede that with CHGPRB to close them first.

Now I took time to have a closer look. Problems have indeed to be closed first, but I can't see how to do that with CHGPRB. Looking and CMDPRB menu, I can't see another helpful command. Even CLO* on the cmdline shows just a command for closing a file.

How can I find out what happens when I select a problem entry in WRKPRB, type 8 and then 20 to close it? Since 8 opens a separate screen, I guess there's some call happening in the background.

Through WRKJOB I could find that the problem database is contained in QUSRSYS/QASXPROB, but I'm not allowed to update it through SQL (UPDATE QASXPROB SET WSXPST='C').

Next would be to search for an API how to do that. The IBM i API finder has an entries for problems:

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/qpdwrkpb.htm
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/pm1b.htm

None of them provides any function to set the status of problems to "closed".

<sigh> Apparently, I need to wade through the 100 or so entries by hand and close them.

Just for the record, this is all in regard to my V4R5 box.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.