×
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.
On 2/9/11 8:23 AM, CRPence wrote:
<<SNIP>> The owner of the object is probably the user that issued
the previously failing\ended request.
Ughh... obviously time for some coffee. While the user name [the
owner name actually, of the object pending the completion of operation]
should appear somewhere in the space, the owner of the recovery object
is always QDBSHRDO [how the creator of that new "share" profile could
possibly forget? ack!]. That is a means to ensure existence regardless
of something as wild as the user who had started the request having been
deleted by DLTUSRPRF. The pending operation must survive pending a
pwrdwn\IPL sequence, so note also that IPL as recovery, given the
operation can be processed [best to investigate origin first; e.g. CRTPF
SIZE(toobig) is going to fail at IPL just as during normal operations],
is much nicer than RCLSTG; that if the IPL does not resolve, then RCLSTG
following the IPL would.
Regards, Chuck
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.
midrange.com
