PM57529: [wi 194243]ISPF daemon fails to start after upgrade to RTC on z/os 3.0.1.2

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

  • After upgrading to IBM Rational Team Concert 3.0.1.2 on z/os
    Build Toolkit, administrators are unable to start the ISPF
    daemon to launch the ISPF client.
    Error received in the ISPFDMN.log is:
     !MESSAGE Application error
     !STACK1
    
     java.lang.RuntimeException: Application
    'com.ibm.team.filesystem.cli.core.id1' could not be found in the
    registry...
    
    During an upgrade to 3.0.1.2, the work directory is not updated
    with the newly upgraded config.ini file, nor is the cache
    cleared in the user directory.
    
    
    To resolve these issues:
    
    1) The config.ini file needs to be copied from the new eclipse
    daemon configuration location to the existing eclipse daemon
    location.
    
     For example,
    
    cp /usr/lpp/jazz/v3.0.1/scmtools/eclipse/daemonconfig/config.ini
    
     /local/jazz/BLZWORK/eclipse/configuration/daemonconfig
    
    The directory names may be different depending on your naming
    scheme.
    
    2) Add or uncomment the -clean parameter in the ispfdmn.conf
    file.
    
    For example,
    
    _ISPF_CLEAN=-clean
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If you type in "scm -clean" the command will fail since you
    have not actually given a command to run.  However, the
    -clean option would have been notice and when the scm
    application is coming up (to subsequently fail) it will
    perform the -clean operation.
    ... so just type in "scm -clean" and ignore the fact that it
    fails
    

Problem conclusion

  • If you type in "scm -clean" the command will fail since you
    have not actually given a command to run.  However, the
    -clean option would have been notice and when the scm
    application is coming up (to subsequently fail) it will
    perform the -clean operation.
    ... so just type in "scm -clean" and ignore the fact that it
    fails
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM57529

  • Reported component name

    RTCZ - TOOLKIT

  • Reported component ID

    5724V8220

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-06

  • Closed date

    2013-08-07

  • Last modified date

    2013-08-07

  • 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

    RTCZ - TOOLKIT

  • Fixed component ID

    5724V8220

Applicable component levels

  • R300 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Team Concert for System z

Software version:

300

Reference #:

PM57529

Modified date:

2013-08-07

Translate my page

Machine Translation

Content navigation