IBM Support

PK80655: sysvar.remoteSystemId only allow 8 character length

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1. What is expected from development? (testfix, how-to, PA (conf
    irm defect), confirm decision)
    Customer is expecting this to be implemented in 7.1.0.3 and if p
    ossible, a fix in 7.1.0.2.
    
    2.Problem statement and description (What is the deviation, erro
    r code, customer Objective)
    In the build descriptor the remoteCall tag of a callLink allows
    for a location setting of PROGRAMCONTROLLED.
    Then, in EGL code, we can use sysvar.remoteSystemId to establish
     the program location
    dynamically. This approach should allow us to externalize the lo
    cation
    of a program and avoid errors in deployment. The problem is that
     the
    sysvar.remoteSystemId only allows for an 8 character system name
    . This
    does not effectively support the location setting as the locatio
    n
    setting can be an IP address or domain-qualified name such as ww
    w.
    mycompany.com (i.e. the location setting in the build descriptor
     allows
    for values larger than 8 characters but the sysvar.remoteSystemI
    d does
    not).
    
    
    3. Current Business impact, future impact and impending deadline
    s.
    Unable to effectively externalize callLink 'location' elements.
    This
    introduces errors in deployments as manual changes are required
    when
    moving from dev to test to prod, etc.
    
    
    4.Products involved and the Version of each product that have th
    e deviation(with iFixes and TestFixes) and which ones don't exhi
    bit the problem?
    RBD 7.1 and RBD 7.5.1
    
    5. Did you try to reproduce? Reproducible or isolated to one mac
    hine, application, workspace (what is unique and distinct about
    it)?
    Did not try to reproduce.
    
    6. If development can reproduce the problem it will improve the
    turnaround time on this escalation. Provide the detailed steps t
    hat development can use to reproduce the deviation.
    N/A
    
    7. Are the test-case/related files(logs directory for IM issues,
     screen-shots) attached to the ER?
    No screenshots, but here is a link to the EGL Cafe thread that t
    hey started:
    http://www-949.ibm.com/software/rational/cafe/thread/1394?tstart
    =0
    
    8.Does the customer have a work around? If yes, provide details.
    Yes, it is specified in the EGL Cafe thread.
    
    9. When did this start happening? Did this always happen? What c
    hanged?
    Always happened.
    
    10. Did you search servdb, rsearch, consult the SME? Any helpful
     results?
    No results.
    

Local fix

Problem summary

  • The SysVar.remoteSystemId field is defined as a CHAR(8)
    which is not long enough for some uses of the field.
    

Problem conclusion

  • For Java target systems, this field has been changed to a
    CHAR(100) to handle longer system ids.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK80655

  • Reported component name

    RATL BUS DEV

  • Reported component ID

    5724S5000

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-13

  • Closed date

    2009-07-23

  • Last modified date

    2009-07-23

  • 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

    RATL BUS DEV

  • Fixed component ID

    5724S5000

Applicable component levels

  • R710 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
06 December 2021