|
Mostly indicative of a PC type job using the file. Try looking at the joblog of the QSERVER job. Often it will indicate which PC is glomming on to the file. Options include: 1) Ending subsystem QSERVER prior to the backup. 2) Using WRKOBJLCK, or an API, and cancelling the exact program prior to the backup. 3) Using save-while-active. But then, to use save-while-active you should be doing journalling and a host of other complexity. 4) Not backup the data 5) Put a MONMSG in there after the SAV... command and skip saving the particular locked files. 6) Other creative opportunities As far as option 5, we had a division that did that. I asked them if I could delete their item master. After all, it was only getting backed up every 8 weeks when we bring the system down in a restricted state. And since we didn't care if it got backed up then the data must be expendable, right? We're kinda big on the endsbs approach. Kinda tricky to sign on to a remote system when QINTER is down. Thank God for SBMRMTCMD and STRSBS QINTER. I know, we could assign a special device to some strange subsystem. But the backup only blows occasionally when a tape fries. luc.lafontan@bbc.co.uk on 01/14/2000 01:39:56 PM Please respond to MIDRANGE-L@midrange.com@Internet To: MIDRANGE-L@midrange.com@Internet cc: Fax to: Subject: New AS-400 Administrator I have an AS-400 9406, 600 running V42. My backups are not completing so I have run them to log and found that I have 12 diagnostic messages resulting from six errors. The six errors are all very similar and have to do with a specific job - 043617/QPGMR/QSERVER The actual message reads: -MESSAGE "Cannot allocate object for file (see list of the six files below) in QUS RSYS -CAUSE " The save operation was not performed for member (file name) in library QUSRSYS type *FILE, because it is allocated by job 043617/QPGMR/QSERVER. Recovery...Try the request again when the object is avalable. Can anyone offer some in sight before calling IBM pay support +--- | 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 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.