Transaction not found on Go Live after Jics Transaction Runner Login.

The "Transaction not found" error you're experiencing after logging in with CC00 on the JICS Transaction Runner during the Go Live phase in AWS is typically caused by an empty transaction database table. This issue can occur in AWS Mainframe Modernization environments where the Blu Age modernized application has been deployed.

To resolve this problem, you should check the following:

1. Verify that your transaction database table is properly populated. In AWS Mainframe Modernization, the transaction data should be migrated to the JICS database.

2. Ensure that you have an SQL file in your S3 bucket dedicated to the deployment of your Blu Age Modernized application. This file should be located at the path jics/sql/initJics.sql and should contain the necessary data to populate the transaction database.

3. If you've confirmed that the database is configured correctly and should contain data, try manually querying the database to check if the data is present.

4. Refresh your browser page, as sometimes this simple action can resolve the issue.

If these steps don't resolve the problem, you may need to investigate further by:

1. Tracing the REST requests made to the back-end in your browser to understand the structure and parameters of the requests.

2. Using a tool like curl to reproduce the same query outside of the browser and analyze the results.

3. Checking the server logs for any error messages that might provide more insight into the issue.

If you're still unable to resolve the issue after trying these steps, it's recommended to open a support case with AWS for more detailed assistance, as some required information may be non-public.
Sources
BluAge L3 Workshop (Go Live --> Testing --> Test Online) Blank Screen when testing Online Transactions CC00 | AWS re:Post
Transaction not found in Blu Age modernized application | AWS re:Post
BluAge L3 Workshop (Go Live --> Testing --> Test Online) | AWS re:Post