跳至內容

TRANBKP script running fine locally but abend in Live

0

As part of L3 workshop, I have tested everything in tomcat/automation then created the live folder and copied required files into S3 bucket. In live application (carddemo-l3-workshop-bk2), online screen is working fine and POSTTRAN job also running fine. But the TRANBKP job is abending with encoding issue ( which was fixed previously by commenting encoding code in application-utility-pgm.yml config file).

Error log of TRANBKP job : -

2025-05-20T12:08:41.962Z INFO ??? --- [ Thread-21] c.n.b.g.r.job.support.GroovyJobExecutor : Groovy script TRANBKP failed [step PRC001] [pgm IDCAMS] [exit code -1] 2025-05-20T12:08:41.962Z ERROR ??? --- [ Thread-21] c.n.b.g.r.job.support.GroovyJobExecutor : Failure cause : java.lang.RuntimeException: org.antlr.v4.runtime.misc.ParseCancellationException: line 1:0 mismatched input 'a@' expecting {<EOF>, DELETE, 'BLDINDEX', DEFINE, 'SET', VERIFY, 'REPRO', 'PRINT', 'IF', 'CANCEL', ALLOC, LISTCAT}

I have retreated the .war file and copied to S3 bucket and re-deployed/restarted the application (carddemo-l3-workshop-bk2). But I am still getting this error. Please help me to resolve this issue.

已提問 6 個月前檢視次數 62 次
1 個回答
0

The issue you're experiencing with the TRANBKP job in the live environment (carddemo-l3-workshop-bk2) appears to be related to character encoding or parsing problems with the IDCAMS commands. This is a common issue that can occur when moving from a local or test environment to a live one, especially if there are differences in how character encoding is handled.

To resolve this issue, you can try the following steps:

  1. Double-check the IDCAMS commands in the TRANBKP script, particularly in the PRC001 step. Look for any unexpected characters or syntax errors that might be causing the parser to fail.

  2. Verify that the encoding of the script files in the live environment matches the expected encoding. Even though you've commented out the encoding configurations in application-utility-pgm.yml, there might still be a mismatch between the file encoding and the system's default encoding.

  3. Review the entire IDCAMS command set in your live scripts for any syntax errors or unexpected characters. Pay special attention to line breaks, spaces, and any special characters that might have been introduced during the transfer to the live environment.

  4. If possible, try to replicate the exact environment and configurations from your successful local tests in the live environment. This includes checking Tomcat versions, Java versions, and any other relevant settings.

  5. Consider adding debug logging or outputting the IDCAMS commands before execution in the live process. This can help you identify any differences between the commands being executed locally versus in the live environment.

  6. If the issue persists, you may need to review the Blu Age runtime configuration for the live environment to ensure it's correctly set up to handle the IDCAMS commands.

  7. As a last resort, you might need to manually edit the IDCAMS commands in the live environment to remove any problematic characters or formatting issues.

Remember that live environments can sometimes behave differently from local or test environments due to subtle differences in configuration or execution context. If these steps don't resolve the issue, you may need to consult with AWS Blu Age support for more specific guidance tailored to your live setup.
Sources
Blu Age L3 Workshop Automation Execute Batch TRANBKP STEP05R REPROC IDCAMS issue | AWS re:Post
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

已回答 6 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。