Updating a log stream's attributes

You can update certain attributes of a DASD-only or coupling facility log stream using either the IXGINVNT UPDATE service or the IXCMIAPU utility. The updates are immediately reflected in the log stream definition in the LOGR couple data set, but some remain pending and do not take effect until specific events occur during processing as described in this section.

Start of changeThe following attributes can be updated while there is an outstanding (active or failed-persistent) connection to the log stream. Some of the updates will not take effect immediately if there is an outstanding connection. In order to update these attributes, the LOGR couple data set must be formatted at least at a certain format level. See LOGR parameters for format utility in z/OS MVS Setting Up a Sysplex for more details.
Note: If this requirement is not met, the UPDATE request fails.
End of change
Pending updates will take effect at different points for each log stream attribute as follows:
  • Start of changeThe RETPD and AUTODELETE attribute updates take effect when a new offload data set is allocated (data set switch event) or on the subsequent first connection to the log stream in the sysplex.End of change
  • The LS_DATACLASS, LS_SIZE, LS_MGMTCLASS, LS_STORCLASSStart of change, and LS_ALLOCAHEADEnd of change attribute updates will remain pending until a new offload data set is allocated (data set switch event) or on the subsequent first connection to the log streamStart of change in the sysplexEnd of change. For a coupling facility log stream, the update also takes effect during the next structure rebuild (user-managed or system-managed).
  • The LOWOFFLOAD, HIGHOFFLOAD, OFFLOADRECALL, STG_DATACLAS, STG_MGMTCLAS, STG_STORCLAS, STG_SIZE, and WARNPRIMARY attribute updates remain pending until the subsequent first connection to the log stream in the sysplex. For a coupling facility log stream, the update also takes effect during the next structure rebuild (user-managed or system-managed).Start of change The STG_DATACLAS, STG_MGMTCLAS, STG_STORCLAS, and STG_SIZE attribute updates are also committed when a new staging data set needs to be allocated following one of the preceding conditions. In the case of a DASD-only logstream, the HIGHOFFLOAD, LOWOFFLOAD, OFFLOADRECALL, and WARNPRIMARY attribute updates are also committed on the next offload data set switch.End of change
  • The LOGGERDUPLEX, STG_DUPLEX, and DUPLEXMODE attribute updatesStart of change for a structure-based logstreamEnd of change remain pending until the subsequent first connection to the log stream in a sysplex or until the next successful structure rebuild (user-managed).
  • The MAXBUFSIZE attribute update remains pending until the subsequent first connection to the DASD-only log stream in the sysplex.
  • The ZAI and ZAIDATA attributes can be updated while there is an outstanding connection to the log stream. In this case, the change will immediately be reflected in the log stream definition. The updated specification will take effect on the following logger events for this log stream:
    1. On the subsequent first connection to the log stream on a system (z/OS image).
    2. As a result of a SETLOGR FORCE,ZAICONN,LSN= command on the target system. or
    3. As a result of a SETLOGR FORCE,ZAICONN,ALL command when there is a connection to this log stream currently using the ZAI=YES setting on the target system.
    Note: Since the updated value can be used on a system by system basis, the installation should ensure the proper actions are taken on all the systems with connections to the log stream in order to make use of the current value.