Look at QUSCHGUS's parameter 5 - Force changes to auxiliary storage
Force changes to auxiliary storage
The method of forcing changes made to the user space to auxiliary storage.
The valid values are as follows:
Does not force changes. Normal system management writes the changes to auxiliary storage.
Forces changes asynchronously. This interrupts the normal system management and ensures that the user space is written to auxiliary storage.
Forces changes synchronously. This interrupts the normal system management and ensures that the user space is written immediately to auxiliary storage.
Or use a pointer to the space (QUSPTRUS api). Obtaining a pointer to the user space will provide virtually immediate update when the value for the space is changed.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Smith
Sent: Thursday, December 04, 2014 12:39 PM
To: Midrange Systems Technical Discussion
Subject: User Space question
This past week our UPS failed, as a result the building lost power and the iSeries (720 , with V7R1) immediately shutdown.
The only "fall out" has been related to several user spaces that we use as "next sequential" number counters.
The value of the user spaces when the system came back up did not reflect updates that had occurred during the day, and as a result various files had duplicate "sequential" numbers.
My question, is there a function for a user space that is similar to FRCRATIO for a database file?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l