× 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.



I think the intent was to remove the existing problem history and then begin
(a fresh) collecting of incidents or inferences of anomalies.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Saturday, May 04, 2013 12:11 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: wrkprb entries ?

On 04 May 2013 03:41, Jack Kingsley wrote:
Thanks for the information, I think the SST route might be the way to
go. I was looking for a simple API call to re-evaluate the system and
then repopulate the WRKPRB screen.

Hmm... So you mean someone did a DLTPRB of *ALL problems, and you want to
get that data back? If so, then from a recent backup taken prior to the
Delete Problem, issue the following request:
?RSTOBJ QASX* QUSRSYS () *FILE OPTION(*OLD) MBROPT(*OLD)
ALWOBJDIF(*NONE)

--
Regards, Chuck
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.