|
Hi Rob A WIld Stab: I don't suppose you use SWA on QUSRSYS ?You will more than likely get more information by looking in the BRMS flight recorders or in the TSM logs on the iSeries; these files live in the IFS; I can't recall the location right now but they have very detailed information. I've been able to figure out a few TSM problems where the job log and BRMS log told me pretty much nothing.
Have a look there to see if that sheds any more light on what is going on. Regards Evan Harris At 04:29 a.m. 30/09/2005, you wrote:
This weekend I received a message CPF414D while using TSM. I do have a pmr open with TSM/IBM, but I thought I'd do a little searching on my own. Found nothing at ibm.com or at google. Message . . . . : Database busy or error occurred Cause . . . . . : The library database was busy or failed with an error during operations on library device TAPMLB01. QUSRSYS must be installed on the system before using a media library device and the following files must be available in QUSRSYS: QATAMID, QLTAMID, QATACGY, QLTACGY, QATAFTR. Recovery . . . : See the previously listed messages to determine the correct database error recovery action. Correct the problem and retry the operation. I've been running TSM for awhile so it's not like the files weren't there. 'available'? Wondered about that. A library save was going on outside of TSM. In the DSPLOG I see shortly before/after this message: ... 70 objects saved from library MGRRPLOBJ. ... Database busy or error occurred ... 4 objects saved from library MGRSAVEGL. ... But QUSRSYS is normally saved around 10:30 am to save files and is, thus, no where near the 00:54 time frame of this error. Therefore I can see no cause for them to be not available. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.