× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Save-while-active problem
  • From: "Edward Koziol" <koziol@xxxxxxxxxx>
  • Date: Wed, 22 Mar 2000 09:42:58 CST
  • Organization: Chaney Systems, Inc.


The first nightly backup after an IPL must always be cancelled and a 
commit job must be ended prior to running the SAVLIB process again.

The command used is:

SAVLIB LIB(*ALLUSR) DEV(TAP01) ENDOPT(*LEAVE) CLEAR(*ALL)
               PRECHK(*YES) SAVACT(*LIB) 


The errors received are:

CPI8367 Save-while-active request for job 067615/PRACCY/PCYASBKP 
ended.  Cause: job ended because all committment definitions with 
pending changes for job were not committed or rolled back before the 
save active wait time (SAVACTWAIT) parameter was exceeded.

CPF377F Save-while-active request prevented by pending record 
changes.

QUESTION:  Is there a procedure that needs to run in order to commit 
                        the changes prior to an IPL when performing 
                        nightly Save-While-Active processes?

Thanks, 

        Ed

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