File Exception when executing the CREASTMT job in CardDemo Blu Age modernized application
Hello Everyone, I am doing L3 Certification workshop and getting the File Exception (Status = 48) : - no root cause error while executing CREASTMT job. I also double checked my CREASTMT.groovy script generated as expected. Does anyone has an idea to solve this issue? Thanks.
Execution Step: https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/execution/test/batch
Error Response
{ "exitCode": -1, "stepName": "STEP040", "program": "CBSTM03A", "status": "Error" }
Tomcat Error Log
2024-10-22T06:42:56.136Z INFO 5780 --- [ Thread-13] .b.c.s.r.AbstractRdbmsPersistenceSupport : Loaded 50 records from AWS_M2_CARDDEMO_ACCTDATA_VSAM_KSDS in 12 ms 2024-10-22T06:42:56.208Z INFO 5780 --- [ Thread-13] c.n.b.gapwalk.io.support.FileFactory : File .\AWS.M2.CARDDEMO.STATEMNT.PS deleted 2024-10-22T06:42:56.208Z INFO 5780 --- [ Thread-13] c.n.b.gapwalk.io.support.FileFactory : File .\AWS.M2.CARDDEMO.STATEMNT.HTML deleted 2024-10-22T06:42:56.249Z INFO 5780 --- [ Thread-13] c.n.b.g.r.job.support.GroovyJobExecutor : Groovy script CREASTMT failed [step STEP040] [pgm CBSTM03A] [exit code -1] 2024-10-22T06:42:56.249Z ERROR 5780 --- [ Thread-13] c.n.b.g.r.job.support.GroovyJobExecutor : Failure cause : com.netfective.bluage.gapwalk.io.exception.LogicErrorException: File Exception (Status = 48) : - no root cause at com.netfective.bluage.gapwalk.io.infrastructure.AbstractFile.a(Unknown Source) at com.netfective.bluage.gapwalk.io.infrastructure.AbstractFile.updateFileStatus(Unknown Source) at com.netfective.bluage.gapwalk.io.infrastructure.AbstractFile.updateFileStatus(Unknown Source) at com.netfective.bluage.gapwalk.io.infrastructure.AbstractSequentialFile.a(Unknown Source) at com.netfective.bluage.gapwalk.io.infrastructure.AbstractSequentialFile.write(Unknown Source) at com.netfective.bluage.gapwalk.io.infrastructure.AbstractSequentialFile.write(Unknown Source) at com.netfective.bluage.gapwalk.io.infrastructure.AbstractSequentialFile.write(Unknown Source) at aws.bluage.l3.workshop.cbstm03a.service.impl.Cbstm03aProcessImpl.createStatement(Cbstm03aProcessImpl.java:230)
- Tags
- AWS Blu Age
- Language
- English
asked 2 years ago226 views
- Newest
- Most votes
- Most comments
Could you please check that you didn't remove the following statement by mistake when running Advanced issues / Control Blocks section?
OPEN OUTPUT STMT-FILE HTML-FILE
If you removed it by mistake, your generated Java code will not have the open file statement and you will have an issue when trying to write one of the files (confirmed by previous comment by @cfrezier)
answered 2 years ago
The error you're encountering while executing the CREASTMT job in the CardDemo Blu Age modernized application appears to be related to a file operation issue. The error message indicates a "File Exception (Status = 48)" with no root cause specified.
Based on the information provided, here are a few points to consider:
-
File Deletion: The logs show that two files (AWS.M2.CARDDEMO.STATEMNT.PS and AWS.M2.CARDDEMO.STATEMNT.HTML) were deleted before the error occurred. Ensure that these files are not required for the job execution or that they are properly recreated if needed.
-
File Permissions: Check if the application has the necessary permissions to create, read, and write files in the required directories. The error could be due to insufficient access rights.
-
Disk Space: Verify that there's enough disk space available on the system where the job is running. A lack of space could prevent file creation or writing.
-
File Naming and Paths: Double-check that the file names and paths in your CREASTMT.groovy script are correct and match the expected locations in the modernized environment.
-
File Status: The error code 48 typically relates to a file status issue. This could mean the file is already in use, locked, or in an unexpected state.
-
Environment Configuration: Ensure that all necessary environment variables or configuration settings required for file operations are correctly set in your AWS Blu Age runtime environment.
-
Data Integrity: Verify that the input data (if any) for the CREASTMT job is correct and in the expected format.
To troubleshoot further:
- Review the CREASTMT.groovy script, focusing on file operations, especially around the CBSTM03A program execution.
- Check the AWS Blu Age runtime logs for any additional error messages or warnings that might provide more context.
- Verify that all required datasets for the test case are properly defined and accessible.
- If possible, try running the job with more detailed logging enabled to get more information about the exact point of failure.
If the issue persists after checking these points, you may need to consult with AWS support or the Blu Age support team for more specific guidance related to your modernized application setup.
Sources
Tutorial: Replay and compare in AWS Mainframe Modernization Application Testing using CardDemo for AWS Blu Age deployed on Amazon EC2 - AWS Mainframe Modernization
RootCauseException - AWS X-Ray
Data structures for AWS Blu Age user - AWS Mainframe Modernization
answered 2 years ago
Hi,
Were you able to fix your problem ? I am facing exactly the same issue
answered 2 years ago
Ok, i found the problem.
After checking that the processed file needed some transformations (removing some "REV0001" in cobol source code), you had to deploy some more code into your environment. It's possible that you forgot to update Cbstm03aProceduredivisionStateMachineService.java This file must contain the opening of file for this exact case.
answered 2 years ago
Relevant content
asked 2 years ago
It's not exactly that, i already replied with the problem i had. But you're right, this would have the same behavior.