IBM Support

Running DXL containing Japanese characters as batch fails with "badly formed token" error

Troubleshooting


Problem

Attempts to run a DXL containing Japanese characters as a batch file results in "badly formed token" error in IBM Rational DOORS.

Symptom

Example error:

-E- DXL: <c:\test3.dxl:1> badly formed token ("/)

In some situation, you may not receive the above error but DXL fails unexpectedly with a different error.

The same DXL works using the Rational DOORS client.

Cause

If a DXL file contains certain Japanese characters which include 0x5c in the double-byte code, DXL considers it as escape characters '/' and fails.

The same problem could potentially happen with other double-byte characters such as Chinese or Korean.

Examples of Japanese characters with 0x5c:

ソ, 構, 十, 申, 能, 表, 予

Diagnosing The Problem

Run the same DXL in Tool > Edit DXL in the Rational DOORS client.

If it returns the same error, DXL actually has the syntax error.

If it works in the client, try the resolution below.

Resolving The Problem

Save the DXL file as UTF-8 character code using a text editor.

[{"Product":{"code":"SSKR2T","label":"IBM Engineering Requirements Management DOORS"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General Information","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.3;9.3.0.1;9.3.0.2;9.3.0.3;9.3.0.4;9.3.0.5;9.3.0.6;9.3.0.7;9.3.0.8;9.4;9.4.0.1;9.4.0.2;9.5;9.5.0.1;9.5.0.2;9.5.1;9.5.1.1;9.5.1.2;9.5.1.3;9.5.2;9.5.2.1;9.5.2.2;9.6","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
01 May 2020

UID

swg21681663

Page Feedback