PM00605: JP - RBD: Generation result shows as error but was OK

APAR status

• Closed as program error.

Error description

• User is generating for iSeries in a DBCS environment.
  
  The generation fails, even though cobol was generated and compil
  e correctly.
  
  
  The problem seems to be that the xml file for the build results
  contains user's DBCS characters from the build server, and parsi
  ng fails.
  
  It could be that we need to change the encoding in the  first li
  ne in the xml file:
  
  ??xml version='1.0' encoding='UTF-8' ??   to whatever is suitabl
  e for the user.
  
  The class CommandOutputList  in distributed build creates this l
  ine: I think it can be modified  to use ResoucesPlugin.getEncodi
  ng() instead of hard coding UTF-8
  
   public void toXML(OutputStreamWriter ps) {
    Trace.enter('CommandOutputList.toXML(PrintStream)', ps);
    if (!imported)
    {
     ps.println('??xml version=\'1.0\' encoding=\'' + ResourcesPlu
  gin.getEncoding() + '\' ??');
  //   ps.println('??xml version=\'1.0\' encoding=\'UTF-8\' ??');
    }
  
  If you can build a fixtest with this change, Mark can  test it h
  ere before sending to the customer.
  
  One thing to watch out for - this should not break EGLSDK. If Re
  sourcesPlugin is not available in EGLSDK, then there needs to be
   additional logic.
  Also, I am not sure if this is the best way to get the encoding.
  

Local fix

Problem summary

• The wrong code page was being used on the server side of the
  build server.
  

Problem conclusion

• Software updated.
  

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

• Fixed component name

  RBD EGL FOR COB

• Fixed component ID

  5724S5001

Applicable component levels

• R751 PSN

     UP