Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

While I am running the first batch job I am getting the below error . I am now to java. Can you please someone explain How can I resolve this error.

0

I am getting the same error after changing to No encoding configurations (NO CP1047, No CP037) in application-utility-pgm.yml and Changed from ZD to CH in TRANREPT STEP05R sort while runnning TRANBKP.groovy job first time.

2025-06-05T00:09:50.579Z INFO 1416 --- [ Thread-15] c.n.b.g.rt.script.ScriptControlTower : Removed jobExecutor [d2e87541-6fbb-4229-8c45-bcc7cb69ea6d] from Script Control Tower. 2025-06-05T00:09:50.579Z INFO 1416 --- [ Thread-15] c.n.b.g.rt.script.ScriptControlTower : Remaining jobExecutors:0 line 1:0 token recognition error at: '' line 1:1 token recognition error at: 'Š' line 1:2 token recognition error at: '€' line 1:3 token recognition error at: 'ä' line 1:4 token recognition error at: '?' line 1:5 token recognition error at: 'ø' line 1:6 token recognition error at: '`' line 1:7 token recognition error at: 'Ê' line 1:8 token recognition error at: 'Ñ' line 1:9 token recognition error at: 'Å' line 1:10 token recognition error at: 'Ç' line 1:11 token recognition error at: 'È' line 1:12 token recognition error at: '€' line 1:13 token recognition error at: ' ' line 1:17 token recognition error at: '?' line 1:14 mismatched input '_/:' expecting {<EOF>, DELETE, 'BLDINDEX', DEFINE, 'SET', VERIFY, 'REPRO', 'PRINT', 'IF', 'CANCEL', ALLOC, LISTCAT}

Topics
Migration & Modernization
Tags
AWS Blu Age
Language
English

asked a year ago119 views

1 Answer
0

The error you're encountering is related to character encoding issues in your TRANBKP batch job. This is a common problem when running Blu Age modernized applications, particularly with IDCAMS utility programs that are part of the batch job.

The specific error shows token recognition errors at various positions, indicating that the parser is encountering characters it cannot properly interpret. The key issue appears to be at line 1:14 with a mismatched input '_/:' that the parser doesn't recognize.

Here are steps to resolve this issue:

  1. Check the content of your IDCAMS control statements in the TRANBKP job. The error suggests there might be a comment starting with '/*' or a line starting with '_/:' that the parser cannot handle.

  2. Review the Groovy script for the TRANBKP job, particularly around line 59 where the error might be occurring (based on similar issues).

  3. If you're using IDCAMS in your job, ensure that any control statements are properly formatted according to the expected syntax.

  4. You've already tried changing encoding configurations and data types (from ZD to CH), which is a good step, but the issue might be with the actual content of the script or control statements.

  5. Download and compare your Groovy scripts with reference scripts if available to identify any discrepancies.

  6. Ensure that the Groovy scripts for TRANBKP are present in the correct directory (usually under WEB-INF/classes/scripts/) and are named correctly.

  7. Check that your application configuration (application.yml or application-utility-pgm.yml) has the proper script locations configured.

This appears to be a syntax issue in the IDCAMS control statements rather than an encoding problem, despite your attempts to fix it by changing encoding configurations.
Sources
Getting below exception while running go-live batch TRANBKP.groovy job. java.lang.RuntimeException: org.antlr.v4.runtime.misc.ParseCancellationException: line 1:0 mismatched input '/*' expecting. | AWS re:Post
Go Live - Post Deployment and Started Application, While trying to submit Batch job, getting as Groovy script unknown/unable to execute. | AWS re:Post

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

Relevant content