AWS BluAge L3 Workshop - Execution - Test - Batch - COMBTRAN - Issue

0

I am running the Blu Age L3 workshop and in the Execution>Test>Batch step (https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/execution/test/batch) when running the COMBTRAN job although the execution finishes successfully, the generated file only contains 2 records, the first one from TRANSACT.BKP and the first one from SYSTRAN, instead of the expected 312 records.

I have checked that I have done the ah-doc modifications indicated in the workshop instructions regarding adding recordSize(350). I have tried to put it in several positions in the groovy script code in case the order influenced it:

.gdgSupport("SORTOUT")
.name("AWS.M2.CARDDEMO.TRANSACT.COMBINED").ownerPath(".").relativeGeneration(1).storageProvider("filesystem")
.recordSize(350)
.disposition("NEW")
.normalTermination("CATLG")
.abnormalTermination("DELETE")
.build()

or

.gdgSupport("SORTOUT")
.name("AWS.M2.CARDDEMO.TRANSACT.COMBINED").ownerPath(".").relativeGeneration(1).storageProvider("filesystem")
.disposition("NEW")
.normalTermination("CATLG")
.abnormalTermination("DELETE")
.recordSize(350)
.build()

I got the same result.

I also tried deleting recordSize(350) as suggested at https://repost.aws/es/questions/QU6YFFigxpTrmjl_ZGNNcXcQ/aws-bluage-l3-workshop-execution-batch-testing-combtran-sort-issue, with the same result.

What else can I check and modify to solve this problem?

Thank you very much

asked 3 months ago123 views
1 Answer
0
  • No, I have tried deleting recordSize and it still generates the file with 2 records instead of the 362 expected.

    So far, I have not been able to solve the problem.

    Any suggestions would be appreciated.

    Thank you

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.

Guidelines for Answering Questions