Skip to content

In AWS Blu Age L3 Workshop I get error when running POSTRAN backend in BAC

1

Error when running POSTRAN { "exitCode": 999, "stepName": "STEP15", "program": "CBTRN02C", "status": "Succeeded" }

2024-11-22 17:21:13.590 INFO 1644 --- [ Thread-14] a.b.l.w.c.s.impl.Cbtrn02cProcessImpl : START OF EXECUTION OF PROGRAM CBTRN02C 2024-11-22 17:21:13.600 INFO 1644 --- [ Thread-14] a.b.l.w.c.s.impl.Cbtrn02cProcessImpl : ERROR OPENING DALYTRAN 2024-11-22 17:21:13.601 INFO 1644 --- [ Thread-14] a.b.l.w.c.s.impl.Cbtrn02cProcessImpl : FILE STATUS IS: 35 2024-11-22 17:21:13.601 INFO 1644 --- [ Thread-14] a.b.l.w.c.s.impl.Cbtrn02cProcessImpl : ABENDING PROGRAM 2024-11-22 17:21:13.601 INFO 1644 --- [ Thread-14] a.b.l3.workshop.core.impl.AbendImpl : ABEND WITH CODE 999

asked a year ago200 views
2 Answers
1
Accepted Answer

It worked after restarting Eclipse with the updated POSTRAN groovy file

answered a year ago
  • This also worked for me. Specifically I had to place the upgraded scripts in carddemo-service\src\main\resources\scripts

0

The error you're encountering in the AWS Blu Age L3 Workshop when running the POSTRAN backend in BAC appears to be related to a file access issue. Specifically, the program CBTRN02C is unable to open the DALYTRAN file, resulting in a file status of 35 and an abend with code 999.

This type of error often occurs when there are issues with file permissions, file paths, or database configurations. To resolve this, you should check the following:

  1. Ensure that all required datasources are correctly configured. This includes checking the configurations for jics, bluesam, bac, and primary datasources.

  2. Verify that the database server is started and running correctly.

  3. Double-check the file paths and permissions for the DALYTRAN file. Make sure the application has the necessary access rights to open and read the file.

  4. If you're using a specific version of the Blu Age tools, ensure that it's compatible with the workshop environment. Some users have reported issues when using mismatched versions.

If the issue persists after checking these points, you may need to review the application configuration files, particularly the application-main.yml file. In some cases, adding the configuration key "stopExecutionWhenProgNotFound: false" to this file has helped resolve similar issues.

If you continue to experience problems, it may be helpful to consult the workshop documentation or reach out to AWS support for further assistance specific to the Blu Age L3 Workshop environment.
Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
BluAge L3 Workshop CEEDAYS Program not found Exception when adding new transaction online | AWS re:Post

answered a year ago
EXPERT
reviewed a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.