RE: Backup blow-up -- MIDRANGE-L

This is APAR SE12151.  If you are on V5R2 you require PTF SI10842.

The problem QSQSRVR job is being used by the Management Central server.
Even if you are ending the MGTC server before the backup this pending change
will not go away.  One workaround is to end the problem QSQSRVR job and that
will cause a rollback.  This did not appear to be a workable option to me
though, because there are usually about 20 QSQSRVR jobs running (and only
one will have the problem.)

The good news is that this is not a serious problem even though you will get
a message stating that your backup "may not be usable."

Be sure to stop the Management Central servers (ENDTCPSVR *MGTC) before you
backup QUSRSYS if you use it SWA.  Also stop any HTTP servers before the SAV
or you will get "Object in use" messages for the log files.

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Thu, 11 Dec 2003 11:30:51 -0500
from: "David A Parnin" <daparnin@xxxxxxxxxxxxxxxxxx>
subject: Backup blow-up

Greetings all,

We're having a problem with our nightly backup.  For years the system had
been set to IPL after the save.  This was done by our predecessors.
Recently we've removed the IPL and added code to restart the things that
were shutdown.  Things have worked great for a couple of weeks but just
started getting the message below.  We don't have any non-system jobs that
do journaling.  Apparently there is a system job QUSER/QSQSRVR that does.
What is this and can it be killed, restarted, or something else that would
allow the backup to run normally?

In case it matters, our SAVLIB command does use save-while-active *SYSDFN.
We don't currently do checkpoint processing but are set to add that soon.
Thanks for any advice that you may have.

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx


                         Additional Message Information
 Message ID . . . . . . :   CPI8365       Severity . . . . . . . :   99
 Message type . . . . . :   Information
 Date sent  . . . . . . :   12/10/03      Time sent  . . . . . . :
20:46:08
 Message . . . . :   Save-while-active request requires commit or rollback
for
   job 029597/QUSER/QSQSRVR.
 Cause . . . . . :   Job 040667/SSA/RBNIGHTLY is performing a save request
that
   has specified SAVACT(*LIB), SAVACT(*SYSDFN) or SAVACT(*SYNCLIB). This
   request cannot continue until all commitment definitions with pending
   changes for job 029597/QUSER/QSQSRVR are committed or rolled back.
Commit
   or rollback operations must be performed so that the objects are saved
   without any uncommitted changes.
 Recovery  . . . :   To allow the save-while-active request to continue, do
the
   following:
     1 - Use the Display Job (DSPJOB) command specifying OPTION(*CMTCTL) to
   display the commitment control status for job 029597/QUSER/QSQSRVR.


===========

                               Display Job Log
                                                             System:
S10A7887
 Job . . :   QSQSRVR       User . . :   QUSER         Number . . . :
029597
     Job 029597/QUSER/QSQSRVR started on 11/30/03 at 16:23:35 in subsystem
       QSYSWRK in QSYS. Job entered system on 11/30/03 at 16:23:34.
     ACGDTA for 029597/QUSER/QSQSRVR not journaled; reason 1.
     User Profile = QSYS
   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail, and delete the original
message.