z/OS DFSMStvs Planning and Operating Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Determining the amount of logging to do

z/OS DFSMStvs Planning and Operating Guide
SC23-6877-00

By logging updates, you can reconstruct data sets from backup copies, if necessary. When you specify the kind of logging that DFSMStvs should do, you must balance the need for logging with the disadvantages of logging. For example, logging can cause performance delays. Delays include the time that it takes to do the logging, from the standpoint of I/O, and the amount of logging that is done.

The recoverability of the data set determines the amount of logging that DFSMStvs does:
LOG(NONE)
The data set is nonrecoverable, and no logging is done. Nonrecoverable data sets are not normally accessed in DFSMStvs mode, but are accessed in DFSMStvs mode if CRE is specified.
LOG(UNDO)
The data set is recoverable and receives only backout logging. Syncpoint processing is done on its behalf, but the data set is not forward recoverable.
LOG(ALL)
The data set is recoverable and receives both backout and forward recovery logging.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014