RE: /Qsys.lib/.lib/ path? -- MIDRANGE-L

Subject: RE: /Qsys.lib/.lib/ path?
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Fri, 29 May 2015 13:06:09 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

One of the profiles is 7 years old and the other is 15. I don't think there's any way to figure out when these files were created.

-----Original Message-----
From: CRPence [mailto:crpbottle@xxxxxxxxx]
Sent: Friday, May 29, 2015 11:52 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: /Qsys.lib/.lib/ path?

On 29-May-2015 11:33 -0500, Justin Taylor wrote:

I now have two users in this state, so I'm going to do a RCLSTG just
in case there are any more.

The system has IPL'd since these users were last active.

That is a likely indication of a pervasive issue that probably should have some investigation performed, and probably some preventive maintenance applied before performing the recovery; i.e. failing to apply what is preventive to issue(s) leaving database files orphaned from their context\library, likely will see the problem recur.

Follow-Ups:

Re: /Qsys.lib/.lib/ path? , Bryan Dietz

This mailing list archive is Copyright 1997-2026 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.