OW45433: CERTAIN AUTOMATION TABLE ENTRIES CAUSE ABENDS0C4 WHEN MULTIPLE VARIABLES ARE USED AND NO ROUTE SPECIFICATION (V1R3 ONLY)

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Certain automation table entries cause an abend 0c4 if there
  are multiple variables used.  Initially seen when automating
  a message that was created using a REXX 'say' instruction.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Tivoli NetView/390 V1R3 who use *
  *                 automation tables.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND0C4 in module DSIFMSGM at offset   *
  *                      x'2FC' when processing an automation    *
  *                      table entry that has exactly 12         *
  *                      parameters in the command portion, and  *
  *                      the fifth entry has a length between 32 *
  *                      and 63 bytes, or between 96 and 127     *
  *                      bytes.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Code was added to V1R3 in module DSIFMSGM to free extra pieces
  of storage if it is currently working on a specific type of IFR.
  If the IFRCODE is IFRCODTI (x'C', or decimal 12) and flag
  IFRTICHC is on (x'20' bit at offset x'39'), then various words
  in the IFR are checked for non-zero, and freed if so. However,
  there are 3 IFR types that do not use an IFRCODE. The parse
  buffer (pointed to by IFRAUPRS) is one of them, and its purpose
  is to hold information about a command to be executed. What most
  IFR structures use as the IFRCODE field is the first 2 bytes,
  but the parse buffer stores the number of parameters in the
  first 2 bytes. So, if the parse buffer contains 12 parameters,
  and the 5th one has a length (found at offset x'38' for 2 bytes)
  that has the x'20' bit on, incorrect 4-byte fields will be
  eligible for freeing, which results in the ABEND0C4. Lengths
  values that have the x'20' bit on are in the range of 32-63,
  96-127, etc. For example, the customer used an automation table
  entry of:
  IF MSGID = 'MEB011'
    & TOKEN(2) = VAR2
    & TOKEN(3) = VAR3
    & TOKEN(4) = VAR4
    & TOKEN(5) = VAR5
    & TOKEN(6) = VAR6
    THEN EXEC(CMD('NB#DUMMY MAJRESNAME='VAR2
                        ' MINRESTYPE='VAR3
                        ' MINRESNAME=WARNING_DURING_SLA_TIME'
                        ' EVENT='VAR4'_'VAR5'_'VAR6
                        ' STATE=WARNING '))
         DISPLAY(Y) HCYLOG(N) NETLOG(Y);
  The fifth entry is the ' MINRESNAME=WARNING_DURING_SLA_TIME',
  which is 35 bytes long. Because there are 12 parameters, and
  the length of the fifth one is in the specific range, the
  ABEND0C4 occurred.
  The same problem can occur with the route list buffer (pointed
  to by IFRAURTL) and the imbedded route list (pointed to by
  IFRAUIRT).
  

Problem conclusion

• Module DSIFMSGM is being changed to separate the code that frees
  chron-type buffers into a new routine, which will be called only
  for buffers that are known to have a valid BUFHDR and IFRCODE
  set up.
  

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:

  UW73113

Modules/Macros

• DSIFMSGM
  

Fix information

• Fixed component name

  TME10NETVIEW S/

• Fixed component ID

  5697B8200

Applicable component levels

• R400 PSY UW73113

     UP00/08/28 P F008

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.