Transformation Center - Transform error

The error you're encountering during the transformation of an RPGLE file in Blu Insights appears to be related to file encoding or parsing issues. While both files have the same encoding (ISO 8859-1) and control codes (CR LF), there might be hidden characters or formatting differences causing the problem.

To resolve this issue, try the following steps:

1. Add a new Metadata section in the Transform step of your workflow with these details:
   • Type: File
   • Name: */
   • Properties: Select the 'encoding' property
   • Order: Move it to the last position
   • Update the property value to 'UTF-8' (Make sure to include the hyphen; 'UTF8' without the hyphen will not work)

This approach addresses potential file encoding issues that can cause the transformation engine to misread or fail to recognize certain elements in your files.

2. If the issue persists, carefully review the content of the problematic file. Look for any hidden characters, unexpected formatting, or syntax errors that might be triggering the NullPointerException.

3. Try removing any comments or non-essential code from the beginning of the file to see if that resolves the issue.

4. Ensure that the file is properly recognized as an RPGLE file by the transformation engine. Check if there are any specific naming conventions or file extensions required.

5. If possible, try transforming a copy of the file with a simpler structure or content to isolate the problem.

6. Check for any recent updates to the Blu Insights transformation engine that might have introduced compatibility issues with certain RPGLE file structures.

If these steps don't resolve the issue, you may need to reach out to AWS support for more specific assistance with Blu Insights transformation errors.
Sources
AWS Blu Age Level 3 Self-Paced Troubleshooting Workshop - Codebase transformation - Transform Error | AWS re:Post
L3 Troubleshooting Workshop- Fatal errors when transforming project scope | AWS re:Post