Specifies the amount of time to wait for an object that is in use, or for transactions with pending changes to reach a commit boundary, before continuing the save operation.
You can specify three wait time elements in the SAVACTWAIT parameter.
The default value is 120 seconds. You can specify the amount of time to wait for the object to become available. You can specify any number of seconds from 0 to 99999 for object locks, or *NOMAX to have the save-while-active operation wait indefinitely. If you end your applications before starting the save operation, specify 0 seconds. If you do not end your applications, specify a value large enough for your applications to make the objects available.
If an object is not available during checkpoint processing, the save-while-active operation will wait up to the specified number of seconds for the object to become available. While waiting for an object, the save operation does nothing else. The save operation may have to wait for several objects. The total time that the save-while-active operation waits may be much longer than the value specified. If an object does not become available within the specified time, the object is not saved, but the save operation continues.
The default value is *LOCKWAIT. You can specify any number of seconds from 0 to 99999 for transactions with pending record changes. You use *NOCMTBDY to save objects without waiting for commit boundaries. If you use *NOMAX, the save-while-active operation will wait indefinitely. If 0 is specified, all objects being saved must be at commit boundaries.
After the save-while-active operation allocates a group of objects that it is synchronizing, it may then wait this many seconds for all jobs that are using the same journals as these objects to reach commitment boundaries. If these jobs do not reach commitment boundaries within the specified time, the save operation ends. After 30 seconds, a CPI8365 message is sent to the QSYSOPR message queue for each job for which the save-while-active operation is waiting.
The default value is *LOCKWAIT. You can specify the amount of time to wait for transactions with Data Definition Language (DDL) object changes or any API commitment resource that is added without the option to allow normal save processing. If you use *NOMAX there is no maximum wait time. You can specify any number of seconds from 0 to 99999. If 0 is specified, and only one name is specified for the Objects (OBJ) parameter, and *FILE is the only value specified for the Object types (OBJTYPE) parameter, the system will save the object without requiring the types of transactions that are listed above to reach a commit boundary.