Skip to content

AWS Blu Age L3 Certification - Test - Batch Execution Fails at step 5. Execute COMBTRAN job

1

Hi All, I am facing issue with Batch Test execution at the step of COMBTRAN in SORT step, Below are the error Messages . I think, its because of File Length 350 have some mismatch from the file creation of previous steps INTCALC or POSTTRAN & TRANBKP steps But I am unable to figure the issue. Can anyone across this issue, Please advise .

Script : http://localhost:8080/gapwalk-application/script/COMBTRAN Response : { "exitCode": -1, "stepName": "STEP05R", "program": "SORT", "status": "Error" }

Error details : 2024-09-30_17-22-59-213 | [JOB] COMBTRAN - Started 2024-09-30_17-22-59-225 | [STEP] STEP05R - Started 2024-09-30T15:22:59.230Z WARN 5220 --- [ Thread-17] c.n.b.g.i.s.c.b.FileConfigurationBuilder : Update of GDGSUpportConfiguration from catalog is not implemented. 2024-09-30T15:22:59.241Z INFO 5220 --- [ Thread-17] c.n.b.g.r.job.support.GroovyJobExecutor : Groovy script COMBTRAN failed [step STEP05R] [pgm SORT] [exit code -1] 2024-09-30T15:22:59.241Z ERROR 5220 --- [ Thread-17] c.n.b.g.r.job.support.GroovyJobExecutor : Failure cause :

groovy.lang.MissingMethodException: No signature of method: com.netfective.bluage.gapwalk.io.support.configuration.builder.GDGSupportConfigurationBuilder.recordsize() is applicable for argument types: (Integer) values: [350] Possible solutions: recordSize(int)

asked 2 years ago312 views

1 Answer
1
Accepted Answer

The error message you've provided indicates that there is an issue with the file length in the COMBTRAN step during the SORT operation. Specifically, the error message suggests that the recordsize() method is not being called correctly, and the expected argument type is an integer.

Here are a few things you can try to troubleshoot and resolve this issue:

Verify File Lengths: Ensure that the file lengths are consistent across the different steps (INTCALC, POSTTRAN, TRANBKP) leading up to the COMBTRAN step. Confirm that the file length of 350 is correct and matches the expectations of the COMBTRAN step.

Check File Configuration: Review the file configuration settings in your COMBTRAN step, particularly the recordSize() method. Ensure that the parameter passed to this method matches the actual file length of 350.

Investigate the GDGSUpportConfiguration: The warning message in the log suggests that the update of the GDGSUpportConfiguration from the catalog is not implemented. This could be causing issues with the file configuration. Check if there are any additional settings or configurations related to the GDGSUpportConfiguration that need to be addressed.

Review the SORT Step Configuration: Examine the configuration of the SORT step in your script. Ensure that the input and output files, as well as the sorting criteria, are correctly defined and aligned with the file structure.

Validate the Groovy Script: Carefully review the COMBTRAN Groovy script to ensure that the file handling and record size configuration are implemented correctly. Check for any typos or syntax errors that could be causing the issue.

Consult Documentation and Seek Support: Refer to the documentation or seek support from the vendor or community to better understand the expected file configuration and SORT step requirements for the COMBTRAN step.

By addressing these potential issues, you may be able to resolve the file length mismatch and successfully execute the COMBTRAN step within the SORT operation.

answered 2 years 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.