Deb,

I recall seeing a similar message when I used the GO BACKUP options to do my 
saves on some CISC boxes.  As far as I know it didn't impact anything.

Have you considered using a different backup strategy (e.g., GO SAVE).  The GO 
BACKUP option is pretty old and I don't believe it's being maintained by IBM 
any longer.



Todd Kidwell (Netstar)
AS/400 System Administrator

>>> "Turner, Deb" <turnerd@bluffton.edu> 03/07/00 09:38AM >>>
  After my first daily backup since upgrading to V4R4 I received the
following message. IBM seems to suggest this message has been here since
v3r2 and is just info only. I have never seen this message before!
Everything did save fine except a few objects in qusrsys, so I realize it is
not critical.  Just an inquiring mind that's all !  Anyone have any insight
as to what this message is telling me other than the obvious?

FYI No users signed-on and save only changed objects = N.


 Message ID . . . . . . :   CPI1466       Severity . . . . . . . :   10
 Message type . . . . . :   Information
 Date sent  . . . . . . :   03/07/00      Time sent  . . . . . . :
03:25:04

 Message . . . . :   Job holds large number of locks.
 Cause . . . . . :   The job 060277/QSYSOPR/QEZBKTMTUE has 30000 locks.
30000
   is a suspiciously large number of locks, and it indicates that an
   application may be leaving locks behind.
 Recovery  . . . :   Determine whether the locks are correct for the
   application.  To do this:

     1. Display the job's locks using the Work with Job (WRKJOB) command
with
   job name QEZBKTMTUE, user QSYSOPR, job number 060277, and option *JOBLCK.
       NOTES:
       - WRKJOB may take longer because of the large number of locks
involved.
       - WRKJOB is usable only if the job is still active.

More...
 Press Enter to continue.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Deb

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.