Where is the JICS database containing TRANSACTIONS located in the RDS carddemo database

In AWS Mainframe Modernization, the JICS database containing TRANSACTIONS is not automatically created in the RDS carddemo database. The transaction data for JICS is typically migrated to a dedicated JICS database.

To populate this database with initial transactions, you should have an SQL file in your S3 bucket that is specifically for deploying your Blu Age Modernized application. This file should be located at the path jics/sql/initJics.sql in your S3 bucket.

If you're not seeing the JICS transactions in either the carddemo_primary or carddemo_bluesam databases, it's possible that the initialization script hasn't been run or there was an issue during the migration process.

To resolve this, you should check the following:

1. Ensure that the initJics.sql file exists in the correct location in your S3 bucket.
2. Verify that the SQL file contains the necessary statements to create and populate the JICS transaction table.
3. Check the deployment logs to see if there were any errors during the database initialization process.

If the transaction table is still not present after confirming these points, you may need to manually run the initialization script or contact AWS support for further assistance with your specific Mainframe Modernization setup.

Remember, the exact location and name of the JICS database can vary depending on your specific modernization configuration, so it's important to review your modernization project settings and deployment scripts to understand where the JICS data is supposed to be stored in your particular case.

Sources
Transaction not found in Blu Age modernized application | AWS re:Post