IBM Support

JR29909: AMEND CLIENT SIDE EDITOR SO THAT IT DOES NOT ADD BLANK LINE TO QS FILES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Blank Lines are added to QS files when they are viewed by client
    editor. This in turn causes the rules to fail when they are
    imported across to a different project.
    

Local fix

  • Go into the QS rule files and remove the blank line which is
    created at the bottom of the file.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Editing QS Rules
    ****************************************************************
    PROBLEM DESCRIPTION:
    When job is exported across it adds blank lines to the
    classification file. This in turn will cause the job to fail.
         When exporting a ruleset
    and then importing it it should not addany blanks lines at the
    bottom of Classification file.
    ****************************************************************
    RECOMMENDATION:
    Apply patch .
    Once applied, the customer will need to go back and fix up any
    designs in their source system to remove any extra newlines.
    This change is included in 8.0.1 Fix Pack 2.
    ****************************************************************
    

Problem conclusion

  • The problem is actually in the editing process of QS rules
    rather than import/export, there is just a knock on effect from
    there.
    
    Basically, when a rule is edited, a temporary file is created
     locally, and notepad is used to edit the rule. Unfortunately,
      the process of creating this file appears to be what's
    appendingthe new line. This has a nasty side effect in that
    even if you just view the rule without making changes, the
    editor thinks  there is a change (since with the new line
    added it is now      different) - and it therefore updates the
    design repository!
           So, now when you export to dsx file there
    is an optimization    which says that if the design &
    provisioned content are the sameonly take one of them (since
    these things could be big). If theyare the same then it uses the
    design content and just    post-provisions that on
    import. Interestingly the code that compares the two ignores
    a trailing newline! Which means even   though the provisioned
    file does not have the newline, the   design content is what
    is put in the dsx.  Thus you now have a  dsx file with the
    newline in it that is deployed on the target  system.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR29909

  • Reported component name

    WIS QUALITYSTAG

  • Reported component ID

    5724Q36QS

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-07-17

  • Closed date

    2008-07-28

  • Last modified date

    2009-06-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • CLIENT
    

Fix information

  • Fixed component name

    WIS QUALITYSTAG

  • Fixed component ID

    5724Q36QS

Applicable component levels

  • R801 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVSBF","label":"InfoSphere QualityStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 June 2009