Skip to content

Request for Suggestions to Resolve Issues with Application Options

0

For the carddemo Angular during L3 ..We have encountered issues with two options in the application, and would request your suggestions Option 1:(Account View) Error encountered during run time : java.lang.RuntimeException: No "CACTVWA" map found in "COACTVW" mapset at com.netfective.bluage.gapwalk.rt.jics.bms.MapRegistry.getMap(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.bms.BMSDialogHelper.b(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.bms.BMSDialogHelper.a(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.bms.BMSDialogHelper.a(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.bms.BMSDialogHelper.lambda$buildTransactionResponse$0(Unknown Source) at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:273) at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625) at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921) at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682) at com.netfective.bluage.gapwalk.rt.jics.bms.BMSDialogHelper.buildTransactionResponse(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.LocalTaskRunner$a.onSuccess(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.LocalTaskRunner$a.onSuccess(Unknown Source) at org.springframework.util.concurrent.ListenableFutureCallbackRegistry.notifySuccess(ListenableFutureCallbackRegistry.java:74) at org.springframework.util.concurrent.ListenableFutureCallbackRegistry.addCallback(ListenableFutureCallbackRegistry.java:65) at org.springframework.util.concurrent.ListenableFutureTask.addCallback(ListenableFutureTask.java:63) at com.netfective.bluage.gapwalk.rt.jics.LocalTaskRunner.a(Unknown Source) at com.netfective.bluage.gapwalk.rt.jics.LocalTaskRunner.invoke(Unknown Source) at com.netfective.bluage.gapwalk.application.web.jics.JICSWebController.doCICSDialog(JICSWebController.java:219) at com.netfective.bluage.gapwalk.application.web.WebController.execTransaction(WebController.java:872) at com.netfective.bluage.gapwalk.application.web.WebController.execTransaction(WebController.java:848) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:255) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:188) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:118) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:926) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:831) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1089) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:979) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:914) at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:694) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:885) at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:777) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:223) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)

Option 2 (Account Update): Observed behavior: Redirects to the login screen without any error.

asked 2 years ago108 views

1 Answer
0

For the issues you're experiencing with the CardDemo application during the L3 workshop, here are some suggestions to resolve them:

For Option 1 (Account View): The error message indicates that the "CACTVWA" map is not found in the "COACTVW" mapset. This could be due to a compilation or deployment issue with the BMS (Basic Mapping Support) maps. To resolve this:

  1. Check if you've properly compiled all BMS maps, especially COACTVW.bms.
  2. Verify that the compiled maps are correctly deployed to the appropriate directory.
  3. Ensure that the COACTVW mapset contains the CACTVWA map definition.
  4. Re-compile the BMS maps using the 'compbms' script for COACTVW.bms specifically, and then use 'compbms.all' to compile all BMS maps again.
  5. After recompilation, redeploy the application artifacts using the 'deploy_app' script.

For Option 2 (Account Update): The behavior of redirecting to the login screen without an error message could indicate a session timeout or authentication issue. To troubleshoot this:

  1. Check the application's session timeout settings and increase the duration if necessary.
  2. Verify that the user permissions are correctly set for the account update functionality.
  3. Examine the server logs for any authentication or authorization errors that might not be displayed on the client side.
  4. Ensure that all necessary CICS resource definitions related to the account update function are properly configured and deployed.

For both issues:

  1. Review the ad-hoc modifications you've made during the workshop, particularly those related to Alternate Indexes handling. Ensure that you've correctly removed references to CXACAIX and CARDAIX from the FILE_TABLE in the jics database.
  2. Verify that the jicsFileAix.json file is present in your working directory with the correct content for handling alternate indexes.
  3. Double-check that all COBOL programs, especially those related to account viewing and updating, are properly compiled and deployed.

If these steps don't resolve the issues, you may need to review the entire deployment process, ensuring all steps in the workshop have been followed correctly, including environment setup, compilation of programs, and deployment of application artifacts.
Sources
Tutorial: Set up the CardDemo sample application in AWS Mainframe Modernization Application Testing - AWS Mainframe Modernization
Tutorial: Deploy CardDemo application on NTT DATA - AWS Mainframe Modernization
AWS Blu Age L3 carddemo-web File Error: READ on CXACAIX | AWS re:Post

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