Configuration transformation center Blu Insights - RPGLE

Question

Hi everyone, this question comes from a previous one referring to Transaction Runner JICS with a RPGLE transformed program, because it does not make use of CICS and VSAM, the workshop and most of the documentation refer to COBOL programs, my question is: what configurations or additional steps to perform in Blu Insights in the transformation center configuration to know the transactions to use in the Transaction Runner JICS for a RPGLE program, or what modifications to perform in the transformation center code to know the transactions. What additional configurations or steps need to be performed in Blu Insights in the Transformation Center configuration?  Additionally, is it necessary to make modifications to the transformed code or perform any additional steps to achieve this?

re:Post Agent · Answer

When dealing with RPGLE programs in AWS Mainframe Modernization using Blu Age, the transformation process differs from that of COBOL and CICS transactions. Since RPGLE programs don't use CICS and instead use iSeries technologies, the concept of a "transaction" as used in the COBOL/CICS world doesn't directly apply. However, to integrate these programs into the AWS Mainframe Modernization environment, they need to be mapped to a transaction-like structure.

To configure the Transformation Center in Blu Insights for RPGLE programs, consider the following steps:

1. Ensure that your RPGLE programs and associated display file (DSPF) screens are properly transformed and deployed in the AWS Mainframe Modernization environment.

2. Check for an equivalent to the initJics.sql file for your RPGLE environment. This file typically contains the transaction definitions for the modernized application and should be located in your S3 bucket under the path jics/sql/initJics.sql.

3. If the SQL file doesn't contain entries that map your RPGLE programs to transaction identifiers, you may need to manually add these mappings or adjust your transformation process to generate them.

4. Review your transformation settings and ensure that the RPGLE-specific configurations are correctly applied. The transformation process for RPGLE programs might require different settings or additional steps compared to COBOL programs to properly set up the transaction environment.

5. After transformation, carefully test the output to ensure it matches the original RPGLE program's behavior. You may need to make manual adjustments or use Blu Age's refactoring tools to optimize the generated code for readability and maintainability.

6. Be prepared to review and potentially adjust the generated Java code, especially for complex RPGLE logic that may not have a direct equivalent in Java.

7. Verify that the correct file type classification is set for your RPGLE programs. You may need to launch the classification process again in your codebase project to ensure accurate file type recognition.

8. Check that your transformation workflow includes the appropriate steps for handling RPGLE features. This may involve configuring specific metadata or transformation rules.

If you continue to experience issues after applying these configurations and steps, you may need to consult with AWS support or your transformation team for guidance tailored to your specific RPGLE setup in AWS Mainframe Modernization.  
**Sources**  
[Transaction JICS - RPGLE | AWS re:Post](https://repost.aws/questions/QUb6ANRyzFSh2cbo4dfg_PzA/transaction-jics-rpgle)  
[Best practice for transforming COBOL programs that use Report Writer features in Blu Age | AWS re:Post](https://repost.aws/questions/QUjZBWPf62R82SYwj2gw7T4g/best-practice-for-transforming-cobol-programs-that-use-report-writer-features-in-blu-age)

Configuration transformation center Blu Insights - RPGLE

Relevant content