As400 Daily Backup Error

50 pts.
Tags:
AS/400 backup
AS/400 backup and recovery
AS/400 error messages
iSeries V6R1
Hi, From long time i am facing issue with daily backup using BRMS in multiple lpars.The daily saves are completing with error .I am in search of a permanent solution for this.Our OS level is V6R1. " Message ID . . . . . . . . : CPF377F       Severity . . . . . . . : 60                                                                                          Job . . . : DAILY_BRMS   User . . :  TU            Number . . . . : 419978      Date sent  . . . . . . . . :  8/24/11      Time sent  . . . . . . : 22:27:57    Program  . . . . . . . . . : Q1ARSTHS      Area . . . . . . . . . : *BKU                                                                                                                                                                   Message . . . . :   Save-while-active request prevented by pending record        changes.                                                                       Cause . . . . . :   The save-while-active request ended on library APDBFA          because there are commitment definitions on the system with pending record      changes. "     It would be great if soe one could help me out go get this issue resolved.                                                              

Software/Hardware used:
Soft Ware

Answer Wiki

Thanks. We'll let you know when a new response is added.

<pre>I use…

ENDSBS SBS(QINTER) OPTION(*IMMED)
MONMSG MSGID(CPF0000)

ENDSBS SBS(QUSRWRK) OPTION(*IMMED)
MONMSG MSGID(CPF0000)

ENDSBS SBS(QSERVER) OPTION(*IMMED)
MONMSG MSGID(CPF0000)

SAVLIB LIB(BKP) DEV(TAP01) ENDOPT(*LEAVE) +
SAVACT(*SYNCLIB) SAVACTMSGQ(SYNCBKP) +
ACCPTH(*YES) OUTPUT(*PRINT)

</pre>

Discuss This Question: 12  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    You show part of the description for message identifier CPF377F. Did you see and read the rest of the message? (The "Recovery" part?) Did you follow the instructions for recovery? What actions have already been taken? Tom
    125,585 pointsBadges:
    report
  • wpoulin
    Sybhro, Is it possible to put the system in a Restricted State prior to doing the Save ? Then nothing would be active. Hope this helps, Bill Poulin
    2,480 pointsBadges:
    report
  • IS Questions
    I suggest you end the QINTER subsystem prior to backup or part of your backup is to end the users. We have also this case before and usually users have a lock on commitment definition.
    110 pointsBadges:
    report
  • Jmsci1
    If you are truely doing a save while active backup using brms, 1. shutdown qinter or whatever the interactive subsystem is named (remember to leave a back door or another interactive up that allow you to log in - for troubleshooting purposes. 2. Monitor the msgq that the sync point msg is sent. 3. once the message is rec'd, restart the interactive subsystem. I do this a lot in large end IT shop. Try it. heres a link http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzaiu%2Frzaiurzaiu352.htm
    35 pointsBadges:
    report
  • TomLiotta
    At the moment, there is no reason to believe that any interactive subsystem is involved in the problem except that it is one of the possibilities. If it's not involved, then ending any interactive subsystem won't make any difference. First step is to determine which commitment definitions are involved, and then to determine which jobs created those definitions. ODBC/JDBC jobs through the database server may be more likely causes of interference at that time of day, but there's no way for us to know. The recovery steps in message description CPF377F need to be followed. The results of those actions can be posted back here if further help is needed. Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    Also note that ending QSERVER and/or QUSRWRK subsystems might have no effect. The related host server jobs can run in other subsystems. Further, if any problems are associated with jobs in those subsystems such that the ENDSBS cannot complete successfully, the result can be a required ENDJOBABN or a forced power-down to effect cleanup. Quite possibly, a RCLSTG SELECT(*DBXREF) or RCLDBXREF *FIX would be needed after IPL. IMO, it is better to end the related host servers with ENDHOSTSVR ENDACTCNN(*DATABASE) than simply to issue ENDSBS. If any job in a subsystem is unable to end, then the subsystem cannot end. The subsystem also can't be restarted to handle new work until the problem is resolved. Tom
    125,585 pointsBadges:
    report
  • markmason
    I am trying to replicate a restricted stated so nightly jobs and backups can run in batch. This is what I have, any suggestions to improve? /* End All Subsystem (COMMENTED OUT) */ /* ENDSBS SBS(*ALL) OPTION(*IMMED) */ /* Replace with Individual SBS */ ENDSBS SBS(MFBATCH) OPTION(*CNTRLD) MONMSG MSGID(CPF1054) ENDSBS SBS(QBATCH) OPTION(*CNTRLD) MONMSG MSGID(CPF1054) ENDSBS SBS(QINTER) OPTION(*CNTRLD) MONMSG MSGID(CPF1054) ENDSBS SBS(QUSRWRK) OPTION(*CNTRLD) MONMSG MSGID(CPF1054) ENDSBS SBS(QSERVER) OPTION(*CNTRLD) MONMSG MSGID(CPF1054) DELAY10: DLYJOB DLY(&SECONDS) ENDHOSTSVR SERVER(*ALL) MONMSG MSGID(CPF0000) ENDSBS SBS(MFBATCH) OPTION(*IMMED) MONMSG MSGID(CPF0000) ENDSBS SBS(QCMN) OPTION(*IMMED) MONMSG MSGID(CPF0000) ENDSBS SBS(QBATCH ) OPTION(*IMMED) MONMSG MSGID(CPF1054) ENDSBS SBS(QINTER) OPTION(*immed) MONMSG MSGID(CPF1054) ENDSBS SBS(QUSRWRK) OPTION(*IMMED) MONMSG MSGID(CPF1054) ENDSBS SBS(QSERVER) OPTION(*immed) MONMSG MSGID(CPF1054) ENDSBS SBS(QPGMR) OPTION(*IMMED) MONMSG MSGID(CPF0000) DELAY5: DLYJOB DLY(&SECONDS) /* delay 10 minutes */ /* NEXT */ STRSBS SBSD(QPGMR) /* MONMSG MSGID(CPF1099) EXEC(GOTO CMDLBL(DELAY5)) */ /* CPF1099 = Subsystem not started because system ending */ STRSBS SBSD(QSPL) MONMSG MSGID(CPF1010) CHGMSGQ MSGQ(QSYSOPR) DLVRY(*HOLD) MONMSG MSGID(CPF2451) /* ********************************************************** */ /* Begin End of Day Process * */ /* ********************************************************** */ STRSBS SBSD(QSYS/QSERVER) MONMSG MSGID(CPF0000) STRSBS SBSD(QSYS/QUSRWRK) MONMSG MSGID(CPF0000) /* Start Communications Subsystem. */ STRSBS SBSD(QCMN) MONMSG MSGID(CPF0000) STRSBS SBSD(QINTER) MONMSG MSGID(CPF0000) DLYJOB DLY(&SECONDS) /* delay 5 minutes */ STRTCP MONMSG MSGID(CPF0000) /* ***************************************************************** */ ENDPGM
    10 pointsBadges:
    report
  • TomLiotta
    ...any suggestions to improve? Definitely. Don't use ENDSBS unless you're going to ensure that the jobs in each of those subsystems has ended first. Otherwise, a locked job will make the associated subsystem unusable until you can IPL. Tom
    125,585 pointsBadges:
    report
  • Jfranz
    The whole purpose of Save While Active is to not shut down! You need to address the parms you are using versus the committment control going on in the user library APDBFA. Save While Active is a wonderful thing to use. IBM has considerable documentation & discussion of the issue in the Info Center.
    55 pointsBadges:
    report
  • Tonks
    Exactly Jfranz..... I too have this issue with our backups intermittently. I cannot shutdown any subsytems whilst our backup occurs so the SWA backup method has been perfect for our requirements ( except when this issue occurs!) Frustrating thing for me is when i try to investigate this issue it tells me the joblog for the offending job eg 278260/QUSER/QRWTSRVR doesnt exist so cannot interrogate what this DB2CON session was doing at the time the overnight backup was being run. "This request cannot continue until all commitment definitions with pending changes for job 278260/QUSER/QRWTSRVR are committed or rolled back."  
    20 pointsBadges:
    report
  • TomLiotta
    ...the joblog for the offending job eg 278260/QUSER/QRWTSRVR doesnt exist so cannot interrogate what this DB2CON session was doing at the time the overnight backup was being run.   The joblog probably won't tell you what it's doing even if you could find it. The joblog doesn't record database transactions in any job, not just QRWTSRVR (unless your developers send messages to the joblog). That's what journals are for, not joblogs.   The QRWTSRVR job is the TCP/IP DDM server handling remote DDM or DRDA database accesses. If you have active server jobs doing important updates during the times you want to run backups, you need to understand that you might not be backing up important database files.   If transactions are being sent and not being committed, the database files are not going to be saved whether you use save-while-active or not. Since you can't end subsystems, you might as well get used to the idea that your backups will fail from time to time. The best alternative is to get your developers to run their transactions properly and either COMMIT successful transactions or ROLLBACK unsuccessful ones. The next best option is to end database services before starting your backups.   Instead of trying to look at a joblog, use iSeries Navigator to drill into the connection for your AS/400 into Databases-> [databasename]-> Transactions-> Database Transactions. You can sort the list by job name to find any transactions for jobs named QRWTSRVR. From a terminal, you can run the WRKCMTDFN JOB(QRWTSRVR) command.   It only makes sense to do this at the time the message is sent. It probably won't do any good to look later in the day because everything will be long gone.   Tom
    125,585 pointsBadges:
    report
  • ToddN2000
    We had some similar issues. Some user would forget to sign off at the end of the day and this would cause lock on files. What to did to eliminate some of the proble was to set the system parm for the inactivity timer to 60 minutes QINACTITV.  This may help without the need to end the sub systems.
    8,825 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following