RE: Save-while-active of QUSRSYS versus Management Central

[Edward Koziol <koziol@xxxxxxxxxx>]

Thanks Rob!  Your sarcasm has no power here!  I thought it was great and
makes sense!  I'm just having too much fun!

Ed  

-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Wednesday, February 14, 2001 10:38 AM
To: MIDRANGE-L@midrange.com
Subject: RE: Save-while-active of QUSRSYS versus Management Central



I have a better solution.  Delete these files that are causing you
troubles.  If you don't care if you back them up then the data must not be
worth anything.  The fact that someone is accessing them is meaningless.

I hope this comes across as bitter sarcasm because I intended it to be.
Does bring up a thought though.

Perhaps a better thought might be to fix the application so that it doesn't
defeat the save-while-active.  Commit your data on a timely basis.
Evaluate this along with the SAVACTWAIT parameter.  But if it takes you
longer than the default of 120 seconds to commit your data then you
probably won't ever get it right without fixing your application.

Perhaps my sarcasm was unnecessary.  Now, I'll listen.  How were you
intending on backing up these skipped files if the save-while-active
skipped them?

Rob Berendt

==================
Remember the Cole!


 

                    Edward Koziol

                    <koziol@chaney.net>        To:
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>             
                    Sent by:                   cc:

                    owner-midrange-l@mi        Subject:     RE:
Save-while-active of QUSRSYS versus Management Central   
                    drange.com

 

 

                    02/14/01 10:43 AM

                    Please respond to

                    MIDRANGE-L

 

 





Thanks!  I had this problem occur on a client system and used this command
to bypass their problem.  Another client runs a long running commitment
control application that prevents the SWA from completing normally.  Our
tape management software does allow us to resume the backup, but not until
after this application completes.

IF IBM IS LISTENING!

WOULDN'T ONE THINK THAT IBM WOULD JUST BYPASS THE FILES IT CAN'T SAVE AND
CONTINUE ON WITH THE PROCESS????

It makes sense to me!

ED

-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Wednesday, February 14, 2001 8:38 AM
Subject: Save-while-active of QUSRSYS versus Management Central



Thought I'd forward this on to you.  Had to modify backup program on GDWEB:
------------- 9 data records excluded --------------------------------
/* 02/14/01 by R.Berendt, CDP   GDS,LLC                             */
/*          We were getting message CPF377F while doing a           */
/*          save-while-active of QUSRSYS.  Job causing problems was */
/*          QYPSSRV - Management Central.  Opened pmr 67809,500     */
/*          with IBM.  IBM recognized this problem and recommended  */
/*          that we stop/start the tcp server for management        */
/*          central.                                                */
------------ 94 data records excluded --------------------------------

/*
 |   Stop tcp server for management central to avoid message CPF377F
 |   while doing save-while-active of QUSRSYS.
*/
ENDTCPSVR *MGTC
------------- 8 data records excluded --------------------------------

/*
 |   Start tcp server for management central after doing
 |   save-while-active of QUSRSYS.
*/
STRTCPSVR *MGTC
------------ 47 data records excluded ------------------

I am not a big fan of throwing in MONMSG's everywhere.  I am seeing too
much code with them and frankly I doubt the integrity of the data on some
of our backups and production programs due to this.

Rob Berendt

==================
Remember the Cole!

+---
| 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
+---



+---
| 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
+---