IBM Support

JR44038: SRVC - UPGRADE7X MESSAGE IMPROVMENTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Enhancements to the messages for upgrade7x output,  which will
    empower customer to troubleshoot them self and avoid opening
    PMRs .
    
    1. Prompt for customer to backup the database is not visible if
       the windows  buffer width is long . Customer will assume code
       is doing something and wait for a long time ..
    
    Format the exist text by  to adding  <LF><CR> to  limit each
    line  to 80 columns .
    
    +++++++++++++
    
    2.  Good to see upgrade7x logs are now saved under
       <porfile>/logs wiht the timestamp !  very nice  :)  This will
       help collect all the logs at the same time for analysis.
    
    
    C:\IBM\BPM75\profiles\TProcSrv02\logs\upgrade_7x_Sat-Sep-08-22.3
    4.57-PDT-2012_0.log
    
       Since the old customer and L2 are not aware of the change in
       log location,  they will be wondering where did the logs go ?
        Best to print the location of the log as soon as the
        customer responds with the yes  to the above question.  So
        even
        if the command hangs or they think it is hung, customers can
        check the progress or find the root-cause of the problem ..
    
    Sample :  Like to see the following  printed to the command
    window so uese of the utility is aware where to find detailed
    logs.
    
    upgrade 7x  Logged to
    C:\IBM\BPM75\profiles\TProcSrv02\logs\upgrade_7x_Sat-Sep-08-22.3
    4.57-PDT-2012_0.log
    
      Also open ID defect to update the information center or I can
    add a comment in the IDOC  ..
    
    ++++++++++
    
     3.  Can you print the actual command used by the customer in
        the log.
         We get only the logs from the customer and we have to go
    back and ask the customer what command they actually used.
    Generally we will get logs from multiple attempts.  Undestnding
    command used by the customer will provide hints on the
    root-cause of the problem.
    
    +++++++++++
    
    4.  Can we print to the screen and in the log where are we
    looking for the database information ?  Still the static
    dbDesign file ?  98database.xml file or the datasource.xml file
    ? Where are we looking for the database information in 7511 ?
    Good to see the upgrade7x is validating (make sure nodeName
    server names are correct) all the options before running the
    command.
    
    Sep 9, 2012 12:11:46 AM WARNING:
    com.lombardisoftware.ant.JULDefaultLogger - Process server
    configuration can't be found under
    C:\IBM\BPM75\profiles\TProcSrv02\config\cells\richmandNode12Cell
    \nodes/TestNode1/servers/TestEnv.AppTarget.0/process-center(or
    process-server)
    
    If the database information is wrong there is no good msg
    indicating where are we looking for the information ..
    
    Sample:  Print following to both to command window and also in
    the log
    Process server configuration found under
    C:\IBM\BPM75\profiles\TProcSrv02\config\cells\richmandNode12Cell
    \nodes/TestNode1/servers/TestEnv.AppTarget.0/process-center(or
    process-server)
    
    ++++++++++++++++
    
    5. Finally the 20,000 lines of classloader information over
    shadow any useful information in the log since tracing with
    "FINE" ..
        Not sure if you can somehow suppress these " class
    net.sf.antcontrib.property.PathToFileSet loaded from parent
    loader (parentFirst) msgs ..
        One of the reason the PMR get opened is because
    administrator can not easily find the useful , relevant
    information in the log while quick scan .
    
    It is ok if we can not  suppress the classloader msges , add
    some empty lines between ANT tasks ,, or a big line or something
    ,  so it make it easier to read  the logs to determine were the
    task begins and ends .
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Express, BPM Standard, and     *
    *                  BPM Advanced on 7.5.1.1                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Lack of logging when running            *
    *                      upgrade7x command.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Better logging requested to help with analysis and
    troubleshooting issues that might arise from using upgrade7x
    command.
    

Problem conclusion

  • Logging improved for upgrade7x command.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44038

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-10

  • Closed date

    2013-09-24

  • Last modified date

    2013-09-24

  • 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

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2021