JR30692: THE QUALITYSTAGE 8.0.1 MATCH SPECIFICATION IS IN AN INVALID FORMAT.

APAR status

• Closed as Permanent restriction.

Error description

• Due to the changes made to IBM InfoSphere QualityStage 8.1 to
  support the Provisioned Match Specifications feature, existing
  
  IBM WebSphere, QualityStage 8.0.1 match specifications are not
  totally compatible with InfoSphere QualityStage 8.1.
  
  1. In InfoSphere QualityStage 8.1, if you use a WebSphere
  
  QualityStage 8.0.1 match specification and job without making
  any changes, the job runs without problems.
  
  
  2. In InfoSphere QualityStage 8.1, if you change the Match
  stage
  in a WebSphere QualityStage 8.0.1 job that uses an 8.0.1 match
  specification, the job fails when it is run. The message in the
  
  log file is "Match specification NAME is in an invalid
  format."
  You must update the match specification NAME to the current
  InfoSphere QualityStage format to allow the job to run.
  

Local fix

• The workaround for the second scenario above is:
  
     1. In the IBM? InfoSphere? DataStage? and QualityStage?
        Designer client, go to the Repository view.
  
     2. Double-click Match Specification to open the match
        specification using the Match Designer.
     3. Save the match specification in the Match Designer.
     4. Exit the Match Designer.
     5. From the Designer client Repository view, right-click
  
        Match Specification.
     6. Select Provision All from the menu.
     7. Click OK to provision the match specification for
        InfoSphere QualityStage 8.1.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  QualityStage 8.0.1 users migrating to 8.1.0
  ****************************************************************
  PROBLEM DESCRIPTION:
  The match specifications from V8.0.1 can not be migrated into
  V8.1
  ****************************************************************
  RECOMMENDATION:
  Use the documented workaround from Support
  ****************************************************************
  

Problem conclusion

• A workaround was provided and documented but due to internal
  architecture changes there will not be a permanent fix.
  

Temporary fix

Comments

APAR Information

• 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