IBM Support

II11069: SMFRTEST RETURN CODE NOT CORRECT FOR SOME PRODUCTS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • As described in Chapter 5 of the System Management Facilities
    (SMF) manual, macro SMFRTEST can be used to determine if a
    particular type of SMF record is being recorded.  If a record
    type is not being collected, SMFRTEST should return with a
    return code of decimal 36 (hexidecimal 24).
         Some OEM products that front-end the SMF macro router
    IEEMB838 do not follow this convention.  Even though the
    particular record type is not being recorded, SMFRTEST ends
    with a return code of 0.
         Computer Associates has acknowledged this problem and
    gave the following information to a customer:
    .
       CA frontends IEEMB838 and ALWAYS gives a return code of
       zero to callers of SMFRTEST for record types less than
       or equal to 90, except for 19 and 38, which give the
       proper return code based on the actual recording status
       of the SMF record.
    .
         To see if IEEMB838 is being front-ended, use the IPCS
    command 'L 10?+C4?+7C?' to look at storage.  This will point
    to IEEMB838 if there is no front-ending code.  If it points
    to #CAS9 or EBCSMFEP, then SMFRTEST will end with return code
    zero even though the record is not being recorded.
         APAR II02887 contains additional information on this
    topic.
    ADDITIONAL SEARCH KEYWORDS: RC0 RC00 RC24 RC36
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II11069

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1998-02-23

  • Closed date

  • Last modified date

    1998-02-23

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
23 February 1998