IBM Support

PK70509: CAL CmdExec to retrieve Squid activity state information fails w ith 'Unable to lookup ClearQuest connections'

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • The CAL CmdExec function fails when doing an lsact -l or lsact
    -fmt %[crm_state]p.  This only happens when the UCM project is
    CQ enabled, and CAL is forced to retrieve the record state from
    CQ.  This does not happen when running lsact as a cleartool
    command.
    
    Windows Powershell example:
    
    PS C:\temp> $ct = new-object -com ClearCase.ClearTool
    PS C:\temp> $ct.CmdExec('lsact -fmt `'%[crm_state]p`'
    activity:ACQ00000001@\UCM_P
    VOB')
    The parameter is incorrect.
    Unable to lookup ClearQuest connections.
    Unknown error 0xC0000005
    

Local fix

Problem summary

  • SQUID was rewritten after the McKinley release.  When used
    through Perl the CAL API does not interface with SQUID.
    

Problem conclusion

  • Closing this APAR as No Plans To Fix (NPTF) because (1) of
    the expected risk to the code base posed by a codefix and
    (2) to the workaround of changing the Perl script to make a
    system call when having to interface with Squid instead of a
    CAL call.
    Note:  cqperl needs to be used for any cc/cq interactions in
    a perl script
    
    my $var = qx("cleartool lsact -l
    activity:SQUID00000041@//sdconnor_RATLC01263831_2009c_pvob")
    ;
    or
    my $var = system("cleartool lsact -l
    activity:SQUID00000041@//sdconnor_RATLC01263831_2009c_pvob")
    ;
    both work and return the desired output.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK70509

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    701

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-08-13

  • Closed date

    2009-05-22

  • Last modified date

    2009-05-22

  • 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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 May 2009