OA41420: UNEXPECTED ERROR RUNNING AN IXCMIAPU UPDATE TO UPDATE THE LOG STREAM GROUP ATTRIBUTE FROM PRODUCTION TO TEST

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Executing program IXCMIAPU to update the GROUP attribute of
  a log stream resulted in an unexpected error.  The joblog
  contains the messages IXG002E and IXG003I:
  
  IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=0000000C
  RSNCODE=00000000
  IXG003I LOGR POLICY PROCESSING ENCOUNTERED AN UNEXPECTED ERROR.
  DIAGNOSIS INFORMATION: 0000000C 00000000 05030016 00000000
  
  Logger's handling of the update request needs to get storage
  for a DAX data structure used for communicating with XCF
  when the updated information has to be written out to the LOGR
  couple data set.  The problem occurs because Logger does not
  obtain this storage when the log stream being updated has
  a data set directory extent in use.
  
  Verification:
  The log stream being updated is using data set extents.  This
  can be verified by running IXCMIAPU with REPORT(YES).  Look
  for the in-use number of DSEXTENTs.  For example:
  
   Type                             Formatted              In-use
   -------------------              ---------              ------
   LSR (Log Stream)                      100                   46
   LSTRR (Structure)                      10                    0
   DSEXTENT (Data Set Extent)            100             --->   5
  
  This number should be greater than 0.  Log stream using a
  dataset directory extent can be identified by listing all
  log streams with DETAIL(YES) when running IXCMIAPU.
      LIST LOGSTREAM NAME(*) DETAIL(YES)
  
  In the output, review the LOG STREAM DATA SET INFO: section
  for a column that calls out data set directory extents:
   'Ext.'
  
  Directory extents should be identified with a .00002or .00003,
  etc.  Look for a log stream that shows:
  
  Ext.   <SEQ#>    Lowest Blockid /  Highest GMT /
                   Highest Blockid   Highest RBA
  -----  --------  ----------------  -----------------
  00002  A0000168  00000000017D81C9  02/07/13 22:31:05
  ^^^^^
                   00000000017FA719  00023578
         A0000169  00000000017FB741  02/07/13 22:31:11
                   000000000181DC91  00023578
         .
         .
         .
         .
  00003  A0000170  000000000181ECB9  02/07/13 22:31:17
  ^^^^^
                   0000000001841209  00023578
  
  Confirm that the log stream GROUP attribute did NOT change
  after running the UPDATE.
  
  Additional symptoms:
  Abend0C4 in IXGI3IYT due to a zero DAX PTR.
  

Local fix

• Include a NEWSTREAMNAME in addition to specifying the GROUP
  keyword for the UPDATE statement.  Including NEWSTREAMNAME
  allows the appropriate handling of the request by obtaining a
  DAX buffer before writing the updated data into the couple data
  set.  Since the log stream will be renamed, another UPDATE can
  be made to specify the 'old' log stream name to rename the log
  stream back to the original name.  The steps would look like
  this:
  
  <Step 1>
  UPDATE LOGSTREAM NAME(old.name) GROUP(TEST)
  NEWSTREAMNAME(new.name)
  
  <Step 2>
  UPDATE LOGSTREAM NAME(new.name) NEWSTREAMNAME(old.name)
  
  <Step 3>
  Verify the log stream GROUP attribute has been updated.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of HBB7770 and above supported         *
  *                 releases using System Logger Service         *
  *                 IXGINVNT or the IXCMIAPU utility to          *
  *                 update a log stream GROUP attribute.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: An attempt to update the GROUP          *
  *                      attribute for a log stream using        *
  *                      DSEXTENTs fails with                    *
  *                      RETCODE=0000000C. An ABEND0C4 in        *
  *                      IXGI3IN2 or IXGI3IZT may also be        *
  *                      encountered.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For log streams with over 168 offload data sets (and therefore
  using DSEXTENTs), attempts to update the log stream GROUP
  attribute (i.e. from GROUP(PRODUCTION) to GROUP(TEST)) will
  fail with a RETCODE=0000000C. ABEND0C4 may also be encountered
  in Logger modules IXGI3IN2 or IXGI3IZT.
  
  The error occurs during log stream UPDATE processing when
  logger attempts to update the LOGR couple data set to reflect
  adjustments in GROUP(TEST) resources, but has not obtained the
  necessary internal buffers.
  

Problem conclusion

• The errors in logstream GROUP update processing when a dsextent
  is in use have been fixed.
  
  This fix may be applied to one system at a time in the sysplex.
  
  Systems with and without the fix activated can coexist in the
  same sysplex, although the problem may persist on those systems
  running without the fix.
  
  Additional Searchable keywords:
   SYSPLEXDS
  
  
  RESTART INFO FOR OA41420
  ****************************************************************
  * FUNCTION AFFECTED: BCP                             (OA41420) *
  *                      Logger                                  *
  ****************************************************************
  * DESCRIPTION      : RESTART                                   *
  ****************************************************************
  * TIMING           : Post-APPLY                                *
  ****************************************************************
  In order for this PTF to be fully effective, you must do one
  of the following:
  -- Option A: IPL the system (CLPA is not required)
  
  -- Option B: Restart System Logger (IXGLOGR address space)
     1. Take action to cause any log stream connectors
        to disconnect from their log stream(s).
  
        You can use the following commands to identify any
        connectors and which log streams need attention.
  
  
         Display LOGGER,C,JOB=*
         Display LOGGER,C,LSN=*
  
        When there are no log stream connections remaining
        on the system, IXG601I message output will indicate
        'NO MATCHING INFORMATION FOUND.'
  
     2. Issue a MODIFY LLA,REFRESH and wait for it to complete
        (CSV210I message)
     3. Issue the command FORCE IXGLOGR,ARM and wait for it to
        complete (IXG067E message)
     4. Issue the command START IXGLOGRS to restart system logger
     5. Take action to reconnect to log streams as needed.
  
     Caution: the FORCE IXGLOGR,ARM command (in step 3 above)
     will cause disconnects for active log stream connections and
     log stream requests will fail until logger is restarted.
     Applications with log stream connections may experience
     outages when logger is unavailable. Log streams will need to
     be re-connected when logger is available to resume
     operations.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UA68796 UA68797

Modules/Macros

• IXGI3IN2
  

Fix information

• Fixed component name

  SYSTEM LOGGER

• Fixed component ID

  5752SCLOG

Applicable component levels

• R770 PSY UA68796

     UP13/05/01 P F304

• R780 PSY UA68797

     UP13/05/01 P F304

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.