Transaction JICS - RPGLE

Question

Hi everyone,I have an inquiry regarding the transformation method of an RPGLE program. Given that this program utilizes iSeries technologies and not z/OS, as is the case with COBOL, it does not use CICS, and the data is not stored by VSAM. Rather, it is stored in PF. When executing the program and the initial Transaction Runner JICS screen appears, I am uncertain about the transaction to use. In the case of the Workshop, it displays the transactions of the COBOL program that can be executed. However, in an RPGLE, how would this process work? Would the name of the RPGLE program or the DSPF screen be required?

I have attempted to place the names of the programs and screens, but the system returns an error stating "Transaction not found."

re:Post Agent · Accepted Answer

When dealing with RPGLE programs in AWS Mainframe Modernization using Blu Age, the process is somewhat different from COBOL and CICS transactions. The "Transaction not found" error you're encountering suggests that the system is not properly configured to recognize your RPGLE programs as transactions.

For RPGLE programs, which 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 resolve this issue:

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 if there's an equivalent to the initJics.sql file for your RPGLE environment. This file typically contains the transaction definitions for the modernized application. It should be located in your S3 bucket under the path jics/sql/initJics.sql.

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

4. If you're unsure about the correct transaction identifiers to use, you might need to consult with your transformation team or AWS support to determine how your specific RPGLE programs should be mapped to transactions in the modernized environment.

5. Once you have the correct transaction identifiers, try entering these in the Transaction Runner JICS screen.

If after these steps you're still encountering issues, it may be necessary to 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 in AWS Mainframe Modernization.

Remember, the exact process can vary depending on the specific implementation and version of AWS Mainframe Modernization you're using, so don't hesitate to reach out to AWS support for guidance tailored to your specific setup.  
**Sources**  
[Transaction not found in Blu Age modernized application | AWS re:Post](https://repost.aws/questions/QUWtXZ1X7fQyWwgHfQWpDj6w/transaction-not-found-in-blu-age-modernized-application)  
[L3 Workshop - Go Live - Test Online - Transaction not Found | AWS re:Post](https://repost.aws/questions/QUqJl6d560TK2zFWKdXR2utA/l3-workshop-go-live-test-online-transaction-not-found)

Transaction JICS - RPGLE

Add your answer

Relevant content