Parameters

The parameters for SETLOGR FORCE are:

DEALLOCCURDS or DEALLOC

Directs the system to close and unallocate the current offload data set for the named log stream that is actively connected on the system from which you issued the command. Any advanced-current offload data sets that are allocated and/or opened on the system are also acted upon in the same manner.

The offload data sets are not deleted as part of this request. If the log stream LS_ALLOCAHEAD value is greater than zero (0), then the next log stream offload activity in the sysplex can cause the current and advanced-current offload data sets to be allocated share again.

Since the command takes effect on an actively connected log stream, any subsequent log stream offload activity that runs on the same system can cause this system to allocate (as shared) the current offload data set again and open it for moving log data from the primary/interim storage medium.

See Managing logger log stream data sets in z/OS MVS Setting Up a Sysplex for more information about offload data set handling.

DISCONNECT or DISC

Directs the system to remove (disconnect) all the connections to the named log stream on the system from which you issued the command. Note that the force connections from a system command can affect active connectors (subsystems, applications) to the named log stream. You can use the FORCE, DISCONNECT command before deleting the log stream resource from the LOGR CDS.

When active connectors exist for the log stream, on a system where the force disconnect command is directed, Logger will first quiesce the connectors' activity for the log stream and then disconnect the log stream from the system. If Logger is unable to complete the logstream disconnect on the system, it may be necessary to issue another SETLOGR FORCE,DISCONNECT command.

Issuing the SETLOGR FORCE,DISCONNECT command when an offload is being held up, or a task is not responding, and any of the following messages are present: IXG271I, IXG272E, IXG311I, IXG312E, IXG114A, IXG115A, may cause ABEND47B or other ABENDs. Respond to these messages before issuing the SETLOGR FORCE,DISCONNECT command. See z/OS MVS Setting Up a Sysplex for more information about these messages.

DELETE or DEL

Directs the system to force the deletion of a named log stream from the LOGR couple data set. You can use SETLOGR FORCE,DELETE only to delete a log stream with no connections or with only failed-persistent connections remaining. It may be necessary to use the SETLOGR FORCE,DISCONNECT command on systems where normal log stream disconnections are not responsive.

If you issue the SETLOGR FORCE,DELETE command and the operation is unable to continue after the log stream had already been marked in the LOGR CDS as started to be deleted, then future attempts to connect to the log stream will fail and the log stream delete operation will be re-attempted at that time.

There might be cases when FORCE DELETE completes successfully, but the system is unable to clean up the following resources:

Staging Datasets: Cleanup will be attempted if the logstream is connected to again.
Structure Connections: Cleanup will be attempted if the logstream is connected to again.
Offload Datasets: The dataset resources can be cleaned up manually, by deleting datasets identified as orphans in the IXCMIAPU TYPE(LOGR) LIST Report.

LSNAME or LSN=logstreamname

Identifies the log stream resource to be acted upon.

For SETLOGR FORCE,DELETE commands, logstreamname can include a wildcard character ('*').

The syntax requirements for LSN= or LSNAME= when specifying a wildcard character are as follows:

The keyword value must contain at least the first qualified segment of a logstream name which includes the initial period before the wildcard character.
You can only specify one wildcard character and it must be the last character for the keyword value.

Examples:

The following are valid syntax examples:

LSN=mylog.*
        mylog.stream*
        mylog.streamx.n*

The following are invalid syntax examples:

LSN=*
        mylog*
        mylog.str*m
        mylog.str*m*
        mylog.*.n*

Note: There are no changes to existing command submission requirements when a wildcard is specified. In other words, if SAF is available, the submitter of the SETLOGR command requires Access Authority of UPDATE to the MVS.SETLOGR.LOGR resource. In addition, if there is no decision on a SAF check, command group authority of MASTER is required.

NORECALL or NOREC

Directs system logger to stop waiting on an outstanding asynchronous recall request for the named data set. Consider using this command when any of the following messages are present: IXG281I, IXG271I, IXG272E, IXG311I, IXG312E, IXG114A, or IXG115A. Each of these messages indicates a Logger operation (such as log stream offload) or a Logger service task may not be progressing properly. The DISPLAY LOGGER,STATUS,RECALLS command output in message IXG601I may also indicate data set recalls are not progressing. See "IXG Messages"in z/OS MVS System Messages, Vol 10 (IXC-IZP) for more information about these messages and commands.

If Logger is currently waiting on a recall request for the data set name when NORECALL option on the SETLOGR command is entered, then message IXG280I will not be issued indicating Logger stopped waiting for the data set recall to complete. The Logger operation that was waiting on the recall request will treat this condition as if DFSMShsm had responded with an error for the data set recall.

Note: More than one recall request can exist for the same data set name, as revealed on the IXG601I output. For this case, each system logger operation waiting for a data set to be recalled will treat the condition as if DFSMShsm had responded with an error.

The net result will depend upon which Logger operation was attempting to access the (migrated) data set. Log stream browse requests might receive "gap" type error conditions meaning not all the log data can be browsed (read). Log stream offload failures might also result if an offload data set was migrated and needed to continue moving log data from "interim" storage to "secondary" (DASD) storage. See z/OS MVS System Messages, Vol 10 (IXC-IZP) for more information.

After this command is issued, you should continue monitoring the Logger activities to ensure no unexpected behaviors occur. Particularly, watch for the log stream exploiter that may have been directly affected by the recall request not completing successfully.

If Logger is not currently waiting on a recall for the data set, then the appropriate messages will be issued indicating the command has been completed. The command will have no effect on Logger's processing.

DSNAMEor DSN=datasetname

Identifies the target log stream data set name resource.

ZAIQUIESCE or ZAIQUI

Directs system logger to quiesce connection activity to the IBM zAware server for z/OS® IBM zAware log stream clients on the target z/OS image. When a specific log stream is named on the LSN=keyword and when the log stream has the ZAI=YES specification, then the log stream will be marked as QUIESCED, and it will be disconnected from the IBM zAware server if connected. No z/OS IBM zAware log stream client data will be maintained for the log stream while in the quiesced (socket disconnected) state, meaning the buffers holding the log data for this purpose will be released (freed).

When the ALL keyword is specified with the ZAIQUIESCE option, then any log streams with the ZAI=YES specification that currently have log stream connections on the target z/OS image will be placed in the QUIESCED state as previously described. In addition, the z/OS IBM zAware log stream client manager state will be set as 'NOT AVAILABLE'. Any log streams subsequently connected on this system with the ZAI=YES specification will also be placed in the 'QUIESCED' state.

When the z/OS IBM zAware log stream client manager state changes to 'AVAILABLE', as a result of a SETLOGR FORCE,ZAICONNECT command, then any log streams that are newly connected to the z/OS image with the ZAI=YES specification will be allowed to attempt z/OS IBM zAware log stream client connections with the IBM zAware server. However, any log streams that were affected by the ZAIQUIESCE,ALL command will not be allowed to connect to the IBM zAware server until the appropriate SETLOGR FORCE,ZAICONNECT command is issued for these log streams, or the log stream is disconnected from the z/OS image and is then newly connected after the z/OS IBM zAware log stream client manager state has been set to 'AVAILABLE'.

ZAICONNECT or ZAICONN

Directs system logger to attempt a socket connection from the z/OS image to the IBM zAware server as per the IXGCNFxx SYS1.PARMLIB ZAI specifications for the identified log streams. When the LSNAME keyword is used, then just the specifically named log stream will be acted upon. When the log stream's current definition for ZAI is YES, the z/OS IBM zAware log stream client manager state will be set as AVAILABLE for the z/OS image along with the following actions.

When the ALL keyword is specified with the ZAICONNECT option, then the z/OS IBM zAware log stream client manager state will be set as AVAILABLE for the z/OS image. Then any log stream that is connected and is currently using the ZAI=YES specification on the target z/OS image will be acted upon.

For each affected log stream, the current ZAI and ZAIDATA attributes will first be obtained from the log stream's definition (in the LOGR CDS), and then the necessary z/OS IBM zAware log stream client connect, disconnect (or a combination of both) actions will occur as follows:

When the log stream's current definition for ZAI is YES:

and the socket connection to the IBM zAware server does not yet exist, then one will be attempted.
and the socket connection to the IBM zAware server already exists, then logger will disconnect the z/OS IBM zAware log stream client and attempt a new socket connection to the IBM zAware server.

When the log stream's current definition for ZAI is NO:

and the socket connection to the IBM zAware server already exists, then logger will disconnect the z/OS IBM zAware log stream client.
and the socket connection to the IBM zAware server does not yet exist, then no additional action is required.

ALL

Identifies that all the appropriate log stream resources are to be acted upon for the command request. For the ZAIQUIESCE option, the z/OS IBM zAware log stream client manager state on the z/OS image will be set as 'NOT AVAILABLE' along with action being taken on each z/OS IBM zAware log stream client.

Examples

Example 1: SETLOGR FORCE,DISC,LSN=SYSPLEX.OPERLOG

Initial display shows the logstream is in Disconnect Pending State.

     SY1   d logger,c,lsn=SYSPLEX.OPERLOG
     SY1   IXG601I   12.42.53  LOGGER DISPLAY 459
     CONNECTION  INFORMATION  BY  LOGSTREAM  FOR  SYSTEM  SY1
     LOGSTREAM                     STRUCTURE          #CONN    STATUS
     ---------                     ---------          -----    ------
     SYSPLEX.OPERLOG               LIST01             000001   DISCONNECT PENDING

     NUMBER OF LOGSTREAMS:  000001

Force disconnect command is entered.

     SY1  setlogr  force,disc,lsn=SYSPLEX.OPERLOG
     SY1  IXG651I  SETLOGR  FORCE  DISCONNECT  COMMAND  ACCEPTED
     FOR  LOGSTREAM=SYSPLEX.OPERLOG
     SY1  IXG661I  SETLOGR  FORCE  DISCONNECT  PROCESSED  SUCCESSFULLY
     FOR  LOGSTREAM=SYSPLEX.OPERLOG

A final display command shows the logstream is no longer connected.

     SY1  d logger,c,lsn=SYSPLEX.OPERLOG
     SY1  IXG601I   12.43.15  LOGGER DISPLAY  466
     CONNECTION  INFORMATION  BY  LOGSTREAM  FOR  SYSTEM  SY1
     LOGSTREAM                     STRUCTURE          #CONN   STATUS
     ---------                     ---------          -----   ------
     NO MATCHING INFORMATION FOUND.

Example 2: SETLOGR FORCE,NOREC,DSN=IXGLOGR.TEST102.STREAM01.A0000000

Initial display shows Logger is waiting on an asynchronous data set recall for the PRODUCTION group and not waiting on any data sets for the TEST group.

     SY1  d logger,st,rec
     D LOGGER,ST,REC
     IXG601I   hh.mm.ss  LOGGER DISPLAY
     SYSTEM LOGGER STATUS
     SYSTEM   SYSTEM LOGGER STATUS
     ------   --------------------
     SY1      ACTIVE
              LOGGER DATA SET RECALLS
                GROUP: PRODUCTION
                  SECONDS    DATA SET NAME
                  0000000024 IXGLOGR.TEST102.STREAM01.A0000000
                GROUP: TEST
                  NO DATA SET RECALLS WAITING

Command is entered to force the norecall option for the data set.

     SY1  setlogr force,norec,dsn=IXGLOGR.TEST102.STREAM01.A0000000
     SY1  IXG601I SETLOGR FORCE NORECALL COMMAND ACCEPTED
     FOR  DSNAME=IXGLOGR.TEST102.STREAM01.A0000000
     SY1  IXG280I IXGLOGR RECALL REQUEST STOPPED BY SETLOGR COMMAND
     FOR  DSN=IXGLOGR.TEST102.STREAM01.A0000000
     SY1  IXG661I SETLOGR FORCE NORECALL PROCESSED SUCCESSFULLY
     FOR  DSNAME=IXGLOGR.TEST102.STREAM01.A0000000

A final display command shows that system logger is no longer waiting on an asynchronous data set recall.

     SY1  d logger,st,rec
     D LOGGER,ST,REC
     IXG601I   hh.mm.ss  LOGGER DISPLAY
     SYSTEM LOGGER STATUS
     SYSTEM   SYSTEM LOGGER STATUS
	  ------   --------------------
     SY1      ACTIVE
	           LOGGER DATA SET RECALLS
                GROUP: PRODUCTION
                   NO DATA SET RECALLS WAITING
                GROUP: TEST
                   NO DATA SET RECALLS WAITING

Example 3: SETLOGR FORCE,ZAIQUI,ALL

Force all z/OS IBM zAware log stream clients on the system to quiesce, meaning disconnect and free buffers.

    SY1  SETLOGR FORCE,ZAIQUI,ALL                         
    SY1  IXG651I SETLOGR FORCE ZAIQUIESCE COMMAND ACCEPTED
    FOR ALL LOGSTREAMS                                    
    SY1  IXG371E ZAI LOGSTREAM CLIENT MANAGER UNAVAILABLE.
    REASON:  SETLOGR COMMAND REQUEST.                     
    SY1  IXG382I ZAI LOGSTREAM CLIENT QUIESCED            
    FOR LOGSTREAM SYSPLEX.OPERLOG                         
    REASON:  SETLOGR COMMAND REQUEST.

Example 4: SETLOGR FORCE,ZAICONN,LSN=SYSPLEX.OPERLOG

Force a z/OS IBM zAware log stream client socket connection attempt, if not already connected, for the SYSPLEX.OPERLOG log stream from the target system to the IBM zAware server for the current ZAI IXGCNFxx parmlib options.

    SY1  SETLOGR FORCE,ZAICONN,LSN=SYSPLEX.OPERLOG                   
    SY1  IXG651I SETLOGR FORCE ZAICONNECT COMMAND ACCEPTED           
    FOR LOGSTREAM=SYSPLEX.OPERLOG                                    
    SY1  IXG380I ZAI LOGSTREAM CLIENT ESTABLISHED                    
    FOR LOGSTREAM SYSPLEX.OPERLOG