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

AWS BluAge L3 Workshop: Monthly transaction report output is not getting generated in the working directory

0

When I am trying to generate monthly transaction report, no error is being shown but the output file containing the monthly report is not getting generated in the working directory either. Here are the logs associated with it as shown in the console:

2024-12-06T11:29:08.858Z INFO 6580 --- [ taskExecutor-2] o.e.s.filters.AnnotationSizeOfFilter : Using regular expression provided through VM argument org.ehcache.sizeof.filters.AnnotationSizeOfFilter.pattern for IgnoreSizeOf annotation : ^.*cache..*IgnoreSizeOf$ 2024-12-06T11:29:08.882Z INFO 6580 --- [ taskExecutor-2] org.ehcache.sizeof.impl.JvmInformation : Detected JVM data model settings of: 64-Bit OpenJDK JVM with Compressed OOPs 2024-12-06T11:29:08.955Z INFO 6580 --- [ taskExecutor-2] org.ehcache.sizeof.impl.AgentLoader : Failed to attach to VM and load the agent: class java.io.IOException: Can not attach to current VM 2024-12-06T11:29:08.991Z INFO 6580 --- [ taskExecutor-2] org.ehcache.core.EhcacheManager : Cache 'AWS_M2_CARDDEMO_USRSEC_VSAM_KSDS' created in EhcacheManager. 2024-12-06T11:29:09.019Z INFO 6580 --- [ taskExecutor-2] .b.c.s.r.AbstractRdbmsPersistenceSupport : Loaded 10 records from AWS_M2_CARDDEMO_USRSEC_VSAM_KSDS in 26 ms 2024-12-06T11:29:09.037Z INFO 6580 --- [ taskExecutor-2] c.n.b.g.r.j.io.internal.JicsFileBuilder : [USRSEC] - IMPLICIT OPEN RESULT : JicsResponseCodeHolder [responseCode=NORMAL, resp2=0] 2024-12-06T11:29:09.145Z INFO 6580 --- [ taskExecutor-2] c.n.b.g.r.c.i.ExecutionControllerImpl : Executing program: COMEN01C 2024-12-06T11:29:09.145Z INFO 6580 --- [ taskExecutor-2] c.n.b.g.rt.db.stats.DatabaseStatistics : DATABASE STATISTIC DISABLED 2024-12-06T11:29:09.187Z INFO 6580 --- [ taskExecutor-2] c.n.bluage.gapwalk.rt.jics.internal.a : Task executed; transaction: CC00, execution result: com.netfective.bluage.gapwalk.rt.jics.control.ReturnInfo@676f4e0c 2024-12-06T11:29:09.188Z INFO 6580 --- [ taskExecutor-2] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : removed [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@75d086fc / 2] - [CC00] 2024-12-06T11:29:11.526Z WARN 6580 --- [ Atomikos:2] c.a.icatch.imp.ActiveStateHandler : Transaction 172.31.24.210.tm173348454136200001 has timed out and will rollback. 2024-12-06T11:29:11.776Z INFO 6580 --- [ taskExecutor-3] c.n.b.g.rt.db.stats.DatabaseStatistics : DATABASE STATISTIC DISABLED 2024-12-06T11:29:11.788Z INFO 6580 --- [ taskExecutor-3] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : added [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@5bca383 / 3] - [CM00] 2024-12-06T11:29:11.788Z INFO 6580 --- [ taskExecutor-3] c.n.b.g.r.c.i.ExecutionControllerImpl : Executing program: COMEN01C 2024-12-06T11:29:11.810Z INFO 6580 --- [ taskExecutor-3] c.n.b.g.r.c.i.ExecutionControllerImpl : Executing program: CORPT00C 2024-12-06T11:29:11.810Z INFO 6580 --- [ taskExecutor-3] c.n.b.g.rt.db.stats.DatabaseStatistics : DATABASE STATISTIC DISABLED 2024-12-06T11:29:11.856Z INFO 6580 --- [ taskExecutor-3] c.n.bluage.gapwalk.rt.jics.internal.a : Task executed; transaction: CM00, execution result: com.netfective.bluage.gapwalk.rt.jics.control.ReturnInfo@63645cf7 2024-12-06T11:29:11.856Z INFO 6580 --- [ taskExecutor-3] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : removed [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@5bca383 / 3] - [CM00] 2024-12-06T11:29:13.274Z INFO 6580 --- [ taskExecutor-4] c.n.b.g.rt.db.stats.DatabaseStatistics : DATABASE STATISTIC DISABLED 2024-12-06T11:29:13.279Z INFO 6580 --- [ taskExecutor-4] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : added [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@13edef6f / 4] - [CR00] 2024-12-06T11:29:13.279Z INFO 6580 --- [ taskExecutor-4] c.n.b.g.r.c.i.ExecutionControllerImpl : Executing program: CORPT00C 2024-12-06T11:29:13.283Z INFO 6580 --- [ taskExecutor-4] a.b.l.w.c.s.impl.Corpt00cProcessImpl : PROCESS ENTER KEY 2024-12-06T11:29:13.286Z INFO 6580 --- [ taskExecutor-4] c.n.bluage.gapwalk.rt.jics.internal.a : Task executed; transaction: CR00, execution result: com.netfective.bluage.gapwalk.rt.jics.control.ReturnInfo@2eb252a 2024-12-06T11:29:13.287Z INFO 6580 --- [ taskExecutor-4] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : removed [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@13edef6f / 4] - [CR00] 2024-12-06T11:29:13.880Z INFO 6580 --- [ taskExecutor-5] c.n.b.g.rt.db.stats.DatabaseStatistics : DATABASE STATISTIC DISABLED 2024-12-06T11:29:13.884Z INFO 6580 --- [ taskExecutor-5] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : added [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@e1c36c2 / 5] - [CR00] 2024-12-06T11:29:13.884Z INFO 6580 --- [ taskExecutor-5] c.n.b.g.r.c.i.ExecutionControllerImpl : Executing program: CORPT00C 2024-12-06T11:29:13.888Z INFO 6580 --- [ taskExecutor-5] a.b.l.w.c.s.impl.Corpt00cProcessImpl : PROCESS ENTER KEY 2024-12-06T11:29:13.917Z WARN 6580 --- [ taskExecutor-5] c.n.b.g.r.j.i.s.GapwalkJicsTDQueue : queue declareJOBS 2024-12-06T11:29:13.918Z INFO 6580 --- [ taskExecutor-5] c.n.b.g.r.j.internal.JicsTDQueueBuilder : IMPLICIT OPEN RESULT : JicsResponseCodeHolder [responseCode=NORMAL, resp2=0] 2024-12-06T11:29:13.936Z INFO 6580 --- [ taskExecutor-5] c.n.bluage.gapwalk.rt.jics.internal.a : Task executed; transaction: CR00, execution result: com.netfective.bluage.gapwalk.rt.jics.control.ReturnInfo@60ce0735 2024-12-06T11:29:13.937Z INFO 6580 --- [ taskExecutor-5] c.n.bluage.gapwalk.rt.jics.internal.a : Running Task Registry : removed [com.netfective.bluage.gapwalk.rt.jics.internal.TaskContext@e1c36c2 / 5] - [CR00] 2024-12-06T11:29:18.944Z WARN 6580 --- [ Atomikos:3] c.a.icatch.imp.ActiveStateHandler : Transaction 172.31.24.210.tm173348454878800002 has timed out and will rollback.

Topics
Migration & Modernization
Tags
AWS Blu AgeAWS Mainframe Modernization
Language
English
AWS
asked a year ago177 views
1 Answer
0

Based on the logs provided, it appears that the monthly transaction report generation process is executing without any obvious errors. However, the absence of the output file in the working directory suggests there might be an issue with the file writing process or the specified output location.

Here are a few potential reasons and suggestions to address this issue:

  1. Output directory permissions: Ensure that the application has the necessary write permissions for the working directory where the report should be generated.

  2. Incorrect output path: Verify that the correct output path is specified in the application configuration. The report might be getting generated but saved in a different location than expected.

  3. Disk space: Check if there's sufficient disk space available in the target directory for the report to be written.

  4. Transaction timeout: The logs show a warning about a transaction timing out and rolling back. This could potentially interfere with the report generation process. You may want to investigate if this timeout is affecting the report creation.

  5. Silent failure: The report generation process might be failing silently without throwing an error. Check the application logs for any additional information or warnings that might provide clues about the issue.

  6. Configuration issue: Review the TRANREPT script and ensure it's correctly set up according to the workshop documentation. There might be a misconfiguration in how the report output is handled.

To troubleshoot further:

  1. Double-check the application configuration, particularly the settings related to report generation and output paths.

  2. Add more detailed logging to the report generation process to track its progress and identify where it might be failing.

  3. Verify that all required dependencies and services for report generation are running correctly.

  4. If possible, try generating a report with a smaller data set to see if the issue persists.

If these steps don't resolve the issue, you may need to review the application code responsible for writing the report file or consult with the AWS Blu Age support team for more specific guidance.
Sources
Error while generating transaction report | AWS re:Post
Enable properties for AWS Blu Age Runtime - AWS Mainframe Modernization

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