Skip to content

Blu Age L3 Workshop Automation Execute Batch TRANBKP STEP05R REPROC IDCAMS issue

0

Question: I encounter IDCAMS parsing error during TRANBKP batch execution in automation testing.

Error message: Groovy script **TRANBKP **failed [step PRC001] [pgm IDCAMS] [exit code -1] ParseCancellationException: line 1:14 mismatched input '_/:' expecting {<EOF>, DELETE, 'BLDINDEX', DEFINE, 'SET', VERIFY, 'REPRO', 'PRINT', 'IF', 'CANCEL', ALLOC, LISTCAT} at com.netfective.bluage.parsers.common.exceptions.ParseErrorException.syntaxError(ParseErrorException.java:18) at org.antlr.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41) at org.antlr.v4.runtime.Parser.notifyErrorListeners(Parser.java:544) at org.antlr.v4.runtime.DefaultErrorStrategy.reportInputMismatch(DefaultErrorStrategy.java:327) at org.antlr.v4.runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:139) at antlr.generated.IdcamsParser.statements(IdcamsParser.java:253) at com.netfective.bluage.parsers.idcams.parser.IdcamsPgmParser.parsesAndExtractStatements(IdcamsPgmParser.java:43) at com.netfective.bluage.gapwalk.utility.idcams.IdcamsPgm.execute(IdcamsPgm.java:90) at com.netfective.bluage.gapwalk.program.UtilityPgm.run(UtilityPgm.java:258)

Background: I previously encountered the same issues in the same utility call in the same step during manual batch testing (before the automation). I resolved the issue by removing encoding configurations (CP1047, CP037) from application-utility-pgm.yml. Similar encoding-related errors are now appearing in automation testing.

Setting:

  1. No encoding configurations (NO CP1047, No CP037) in application-utility-pgm.yml
  2. Tomcat 10 used in both carddemo-pom/carddemo-service (manual test ) and carddemo-automation (automation).
  3. Removed sort condition in TRANREPT STEP05R
  4. Changed from ZD to CH in TRANREPT STEP05R sort
  5. All batch scripts are working in the manual test. The IDCAMS character set issue occurs again in the Automation.

Thank you

  • Have you removed the encoding from automation project also ? Full path [D:\PhotonUser\Workshop\workspace\carddemo-automation\tests-cases\00-default\working-directory\config\application-utility-pgm.yml]

  • Rupesh, Thanks. It works. I was wrongly updating the D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\webapps\gapwalk-utility-pgm\WEB-INF\classes\application-utility-pgm.yml (deployed/compiled version). You are right. I should update the source version in the test-cases directory D:\PhotonUser\Workshop\workspace\carddemo-automation\tests-cases\00-default\working-directory\config. Thank you for your help.

AWS
asked 10 months ago245 views
1 Answer
1

The issue you're experiencing with the IDCAMS parsing error during the TRANBKP batch execution in automation testing is likely related to character encoding or syntax problems in the IDCAMS commands.

Even though you've removed the encoding configurations from the application-utility-pgm.yml file, there might still be encoding-related issues in the automation environment. The error message suggests that the parser is encountering unexpected characters ('_/:') where it's expecting specific IDCAMS commands.

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. Ensure there are no unexpected characters or syntax errors.

  2. Verify that the encoding of the script files in the automation environment matches the expected encoding. Even if you've removed specific encoding configurations, there might be a mismatch between the file encoding and the system's default encoding.

  3. Review the entire IDCAMS command set in your automation scripts for any syntax errors or unexpected characters. Pay special attention to line breaks and spaces, as these can sometimes cause parsing issues.

  4. If possible, try to replicate the exact environment and configurations from your successful manual tests in the automation 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 automation process. This can help you identify any differences between the commands being executed in manual testing versus automation.

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

Remember that automation environments can sometimes behave differently from manual testing 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 or your workshop facilitators for more specific guidance tailored to your automation setup.
Sources
Unloading issue during automation process in L3 Workshop | AWS re:Post
L3 Workshop - CREASTMT - Batch Job - Failing in the very first step - { "exitCode": -1, "stepName": "DELDEF01", "program": "IDCAMS", "status": "Error" } | AWS re:Post
AWS Blu Age FAQ - AWS Mainframe Modernization

answered 10 months ago
  • Added some debug println before the execute of IDCAMS, not sure it if provide additional hints :

    Debug: CNTLLIB value = AWS.M2.CARDDEMO.CNTL Debug: Job Context = TRANBKP Debug: File Configurations: PRC001.FILEIN: BluesamFileConfiguration [bluesamId=, dataset=AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS, cacheCompression=false, warmUp=true, isAnsiCarriageControl=false, disposition=SHR, normal termination=KEEP, abnormal termination=KEEP] PRC001.FILEOUT: GDGSupportConfiguration [relativeGeneration=1, name=AWS.M2.CARDDEMO.TRANSACT.BKUP, ownerPath=., cacheCompression=false, warmUp=true, storageProvider=filesystem, recordSize=350, jobContext=com.netfective.bluage.gapwalk.rt.job.support.DefaultJobContext@5b428702, rdw=false, bdw=false, isFixed=false, isLF=false, isCRLF=false, isMicroFocusCompatible=false, order=LIFO] Debug: SYSIN path = AWS.M2.CARDDEMO.CNTL(REPROCT) Debug: Parameters: MapTransfo: [:] -->(MapTransfo is empty)

    No encoding configurations (NO CP1047, No CP037) in application-utility-pgm.yml

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.