IBM Support

IT35854: FDC generated when runamscred is run with no parameters

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

  • Closed as program error.

Error description

  • If the runamscred command is run with no parameters, then the
    command will correctly display its usage information. However,
    an FDC is also generated. The FDC contains the following
    information:
    
    ----------------------------------------------------------
    ...
    Source Class     :-
    com.ibm.msg.client.commonservices.j2se.NLSServices
    Source Method    :- getMessage(String,Object[])
    ProbeID          :- XS001002
    Thread           :- name=main priority=5 group=main
    ccl=sun.misc.Launcher$AppClassLoader@53a27570
    ...
                        Stack trace
                        -----------
    
    Stack trace to show the location of the FFST call
    |   FFST Location  :-  java.lang.Exception
    |       at
    com.ibm.msg.client.commonservices.trace.Trace.getCurrentPosition
    ()
    |       at
    com.ibm.msg.client.commonservices.trace.Trace.createFFSTString()
    |       at
    com.ibm.msg.client.commonservices.trace.Trace.ffstInternal()
    |       at com.ibm.msg.client.commonservices.trace.Trace.ffst()
    |       at
    com.ibm.msg.client.commonservices.j2se.NLSServices.getMessage()
    |       at
    com.ibm.msg.client.commonservices.j2se.NLSServices.getMessage()
    |       at
    com.ibm.msg.client.commonservices.nls.NLSServices.getMessage()
    |       at com.ibm.mq.ese.core.AMSExceptionDetails.getMsg()
    |       at com.ibm.mq.ese.core.AMSExceptionDetails.getMsg()
    |       at com.ibm.mq.ese.core.AMBIException.<init>()
    |       at com.ibm.mq.ese.config.ConfigException.<init>()
    |       at
    com.ibm.mq.ese.config.KeyStoreConfigProtector.readArgs()
    |       at com.ibm.mq.ese.config.KeyStoreConfigProtector.main()
    
    ----------------------------------------------------------
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This affects users who use the runamscred command.
    
    
    Platforms affected:
    AIX, Linux on Power, Windows, Linux on zSeries, Linux on x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the runamscred command was run without any parameters, it
    incorrectly attempted to get the usage information to display to
    the user twice. The first time would work. However, when the
    command tried to get the usage information for the second time,
    a NullPointerException occurred which resulted in an FDC being
    generated containing the information shown below:
    
    ----------------------------------------------------------
    ...
    Source Class     :-
    com.ibm.msg.client.commonservices.j2se.NLSServices
    Source Method    :- getMessage(String,Object[])
    ProbeID          :- XS001002
    Thread           :- name=main priority=5 group=main
    ccl=sun.misc.Launcher$AppClassLoader@53a27570
    ...
                        Stack trace
                        -----------
    
    Stack trace to show the location of the FFST call
    |   FFST Location  :-  java.lang.Exception
    |       at
    com.ibm.msg.client.commonservices.trace.Trace.getCurrentPosition
    ()
    |       at
    com.ibm.msg.client.commonservices.trace.Trace.createFFSTString()
    |       at
    com.ibm.msg.client.commonservices.trace.Trace.ffstInternal()
    |       at com.ibm.msg.client.commonservices.trace.Trace.ffst()
    |       at
    com.ibm.msg.client.commonservices.j2se.NLSServices.getMessage()
    |       at
    com.ibm.msg.client.commonservices.j2se.NLSServices.getMessage()
    |       at
    com.ibm.msg.client.commonservices.nls.NLSServices.getMessage()
    |       at com.ibm.mq.ese.core.AMSExceptionDetails.getMsg()
    |       at com.ibm.mq.ese.core.AMSExceptionDetails.getMsg()
    |       at com.ibm.mq.ese.core.AMBIException.<init>()
    |       at com.ibm.mq.ese.config.ConfigException.<init>()
    |       at
    com.ibm.mq.ese.config.KeyStoreConfigProtector.readArgs()
    |       at com.ibm.mq.ese.config.KeyStoreConfigProtector.main()
    
    ----------------------------------------------------------
    

Problem conclusion

  • The runamscred command has been updated so that if it is run
    without any parameters, it only gets the usage information once.
    This prevents the FDC mentioned in this APAR from being
    generated.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.3
    v9.x CD    9.2.1
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT35854

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-02-10

  • Closed date

    2021-03-03

  • Last modified date

    2021-07-02

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

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

Fix information

  • Fixed component name

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Type":"MASTER","Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
03 July 2021