- Newest
- Most votes
- Most comments
I encountered the same issue. As noted by @cfrezier in its last comment. The reason is that the data were loaded using the "local" method. Which is the method highlighted in the correction video.
I don’t know why, but the data are like loaded with the wrong record size, which corrupt it in the database.
To solve this issue, you need to clear the data, then reload it using the "server" method. Thus, the data are loaded correctly.
answered a year ago
Could you please confirm that you have checked the initial state before running the batch, especially Bluesam datasets? https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/execution/test/batch
Records should be present in datasets used by POSTTRAN batch (e.g. account).
answered 2 years ago
Based on the logs you've provided, it appears that all 300 transactions processed by the CBTRN02C program in the POSTTRAN job were rejected. This is likely causing the issue where no transactions are being added to the TRANSACT.VSAM.KSDS file, preventing you from proceeding with subsequent steps.
There are a few things you can check to troubleshoot this issue:
-
Verify that all required datasources are correctly configured. This includes checking the configurations for jics, bluesam, bac, and primary datasources.
-
Ensure that the database server is started and running correctly.
-
Double-check the file paths and permissions for the input files and the TRANSACT.VSAM.KSDS file. Make sure the application has the necessary access rights to read from and write to these files.
-
Review the POSTTRAN groovy file for any potential issues or misconfigurations.
-
If you've made any recent changes to the configuration or code, try reverting them to see if that resolves the issue.
-
Check if there are any specific validation rules in the CBTRN02C program that might be causing all transactions to be rejected. You may need to review the program logic to understand why the rejections are occurring.
If the issue persists after checking these points, you might want to try restarting Eclipse with the updated POSTTRAN groovy file, as this has resolved similar issues for other workshop participants.
If you continue to experience problems, it would be advisable to consult the workshop documentation or reach out to AWS support for further assistance specific to the Blu Age L3 Workshop environment.
Sources
In AWS Blu Age L3 Workshop I get error when running POSTRAN backend in BAC | AWS re:Post
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
answered 2 years ago
Relevant content
asked 2 years ago
asked a year ago
- AWS OFFICIALUpdated 2 years ago

The content of the files using the "server" / "local" methods to load data in BAC did not result in the same data loaded (even if I was selecting the same files). Strange but this was the origin of the error.