IBM Support

IT01263: EXPORT SERVICE FAILS TO EXPORT SSH REMOTE PROFILE WHEN THE NAME CONTAINS UNDERSCORES

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

  • Problem Description:
    Export Service fails to export SSH Remote Profile when the
    Name contains an underscore. The export completes successfully
    but the remote profile is not exported.
    

Local fix

  • STRRTC - 420118
    PC / PC
    Circumvention:
    
    Add a backslash as an escape character before each underscore in
    the name (in the XML input file). The export service will
    export the remote profile if the input file includes all SSH
    Remote Profiles (<include>*</include>). Also, Resource Manager
    will export the remote profile.
    
    <?xml version="1.0" ?>
    <ExportConfiguration>
       <OutputFormatType>XML Document</OutputFormatType>
    
    <ExportResourcesBasedOnTagName>No</ExportResourcesBasedOnTagName
    >
       <ExportType>Standard</ExportType>
       <Resources>
           <Resource>
              <Name>SCI_SSH_REMOTE_PROFILES</Name>
              <PatternSet>
                <include>XS\_AFT\_SSH\_Profile</include>
              </PatternSet>
         </Resource>
       </Resources>
       <Passphrase>
          <SecurityContext>XXX</SecurityContext>
          <SecurityIdentity>XXXXX</SecurityIdentity>
          <ExportCertificate>Yes</ExportCertificate>
       </Passphrase>
    </ExportConfiguration>
    

Problem summary

  • PROBLEM SUMMARY
    USERS AFFECTED:
    ALL
    
    PROBLEM DESCRIPTION:
    EXPORT SERVICE FAILS TO EXPORT SSH REMOTE PROFILE WHEN THE
    NAME CONTAINS UNDERSCORES.
    
    PLATFORMS AFFECTED:
    ALL
    

Problem conclusion

  • PROBLEM CONCLUSION
    
    RESOLUTION SUMMARY:
    THIS ISSUE IS DB SPECIFIC AND IS CAUSED BECAUSE OF NOT ESCAPING
    THE SPCEIAL CHARACTER(\) IN THE SQL QUERIES. A CODE CHANGE HAS
    BEEN MADE SO THAT THIS CHARACTER IS ESCAPED FROM THE SQL
    QUERIES.
    
    DELIVERED IN:
    5020500_2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT01263

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    524

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-24

  • Closed date

    2015-02-16

  • Last modified date

    2015-02-20

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R525 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.4","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
20 February 2015