CA InterTest

Expand all | Collapse all

CA InterTest don't work (CAVHCONF)

Jump to Best Answer
  • 1.  CA InterTest don't work (CAVHCONF)

    Posted 08-18-2017 12:17 PM

    Hi,

    I have istalled to my workstation CA InterTest™ and CA SymDump® Common User Interface.

    I also added host server and made batch project.

    When I tried to load data from PROTSYM file or anything else I did't get answer from host server.

    It look's that problem is in Mainframe.

    Does anyone know what is the problem?

    BR

    Timo Mäenpää

    timo.t.maenpaa@cgi.com

     

    Error message  

     

    Next one is from CAVHSRVR job from DDname STDERR

    CAVHSRVR

    DD STDERR

    2017/08/18 18:41:21 I: Seq:29 Session 10.129.98.5-23582-29 Started              <=com.ca.intertest.services.ServerRunner <init>

     2017/08/18 18:41:25 I: Seq:30 Session 10.129.98.5-23590-30 Started              <=com.ca.intertest.services.ServerRunner <init>

     2017/08/18 18:41:25 I: CVMO packet WriteOut                                     <=com.ca.intertest.services.ServerRunner WriteOut

     2017/08/18 18:41:25 I: Seq:30 10.129.98.5-23590-30 CVMO buffer:

     +0000 00000008 00000000                                                       !........                        ! <=com.ca.intertest.

     services.ServerRunner WriteOut

     2017/08/18 18:41:25 I: CVMO packet WriteOut                                     <=com.ca.intertest.services.ServerRunner WriteOut

     2017/08/18 18:41:25 I: Seq:29 10.129.98.5-23582-29 CVMO buffer:

     +0000 00000008 00000000                                                       !........                        ! <=com.ca.intertest.

     services.ServerRunner WriteOut

     

    Error log from my computer:

     


    !SESSION 2017-08-18 18:41:00.848 -----------------------------------------------
    eclipse.buildId=unknown
    java.version=1.6.0_27
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fi_FI
    Command-line arguments: -os win32 -ws win32 -arch x86

    !ENTRY org.eclipse.ui 4 4 2017-08-18 18:41:14.563
    !MESSAGE MenuAdditionCacheEntry.mergeIntoModel: Invalid menu URI: com.ca.intertest.cics.menuContribution1

    !ENTRY com.ca.intertest 1 0 2017-08-18 18:41:16.710
    !MESSAGE com.ca.intertest Started

    !ENTRY com.ca.intertest 1 0 2017-08-18 18:41:17.079
    !MESSAGE Debugger is listening on port 64475 PreferIPv6 Addresses

    !ENTRY com.ca.testingtools 2 900 2017-08-18 18:43:37.646
    !MESSAGE Exception Connection reset detected while execution cmnd=check&user=TXM&epassw=************
    com.ca.testingtools.core.ServerConnect connect

    !ENTRY com.ca.testingtools 4 1000 2017-08-18 18:43:37.661
    !MESSAGE Connection reset
    com.ca.testingtools.ui.dialogs.UserLogonDialog okPressed
    !STACK 0
    java.lang.Throwable: Error attempting to connect to server
    at com.ca.testingtools.ui.dialogs.UserLogonDialog.okPressed(UserLogonDialog.java:248)
    at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
    at org.eclipse.jface.window.Window.open(Window.java:801)
    at com.ca.testingtools.core.TTServer$1.run(TTServer.java:276)
    at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164)
    at org.eclipse.ui.internal.UILockListener.aboutToWait(UILockListener.java:126)
    at org.eclipse.core.internal.jobs.LockManager.aboutToWait(LockManager.java:123)
    at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:845)
    at org.eclipse.core.internal.jobs.InternalJob.join(InternalJob.java:380)
    at org.eclipse.core.runtime.jobs.Job.join(Job.java:385)
    at com.ca.intertest.server.ServerElement.checkPint(ServerElement.java:643)
    at com.ca.intertest.server.ServerElement.isEnabled(ServerElement.java:713)
    at com.ca.intertest.ui.actions.ConfigureBreakpointAction.run(ConfigureBreakpointAction.java:128)
    at com.ca.intertest.ui.actions.ConfigureBreakpointAction.doubleClick(ConfigureBreakpointAction.java:264)
    at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:845)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
    at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:843)
    at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1477)
    at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1246)
    at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249)
    at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:246)
    at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:307)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at com.ca.intertest.rcp.Application.start(Application.java:48)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

    !ENTRY com.ca.testingtools 2 900 2017-08-18 18:43:49.439
    !MESSAGE Exception TTLoginCancelledException detected while execution null
    com.ca.testingtools.core.ServerConnect connect

    !ENTRY com.ca.testingtools 2 900 2017-08-18 18:46:39.600
    !MESSAGE Exception Connection reset detected while execution cmnd=check&user=TXM&epassw=***************
    com.ca.testingtools.core.ServerConnect connect

    !ENTRY com.ca.testingtools 4 1000 2017-08-18 18:46:39.603
    !MESSAGE Connection reset
    com.ca.testingtools.ui.dialogs.UserLogonDialog okPressed
    !STACK 0
    java.lang.Throwable: Error attempting to connect to server
    at com.ca.testingtools.ui.dialogs.UserLogonDialog.okPressed(UserLogonDialog.java:248)
    at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
    at org.eclipse.jface.window.Window.open(Window.java:801)
    at com.ca.testingtools.core.TTServer$1.run(TTServer.java:276)
    at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164)
    at org.eclipse.ui.internal.UILockListener.aboutToWait(UILockListener.java:126)
    at org.eclipse.core.internal.jobs.LockManager.aboutToWait(LockManager.java:123)
    at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:845)
    at org.eclipse.core.internal.jobs.InternalJob.join(InternalJob.java:380)
    at org.eclipse.core.runtime.jobs.Job.join(Job.java:385)
    at com.ca.intertest.server.ServerElement.checkPint(ServerElement.java:643)
    at com.ca.intertest.server.ServerElement.isEnabled(ServerElement.java:713)
    at com.ca.intertest.ui.actions.ConfigureBreakpointAction.run(ConfigureBreakpointAction.java:128)
    at com.ca.intertest.ui.actions.ConfigureBreakpointAction.doubleClick(ConfigureBreakpointAction.java:264)
    at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:845)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
    at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:843)
    at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1477)
    at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1246)
    at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249)
    at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:246)
    at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:307)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at com.ca.intertest.rcp.Application.start(Application.java:48)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

    !ENTRY com.ca.testingtools 2 900 2017-08-18 18:47:26.056
    !MESSAGE Exception TTLoginCancelledException detected while execution null
    com.ca.testingtools.core.ServerConnect connect

     



  • 2.  Re: CA InterTest don't work (CAVHCONF)
    Best Answer

    Broadcom Employee
    Posted 08-18-2017 01:13 PM

    Hello Timo.  Thank you for reaching out to the community.  

     

    The system that you're connecting to has not yet been initialized for CA InterTest and/or CA SymDump use.  Please refer to the CAIRIM section of the documentation here:

     

    Activate Your Product - CA InterTest™ and CA SymDump® - 10.0 - CA Technologies Documentation 

     

    Be sure that your CA InterTest and/or CA SymDump options in CAVHCONF have been properly customized before activating the products.

     

    Michael DuBois



  • 3.  Re: CA InterTest don't work (CAVHCONF)

    Posted 08-21-2017 05:29 AM

    Dear Michael and Timo,

     

    I think I am the support member, who made the installation of Intertest Batch 10.0 user interface for Timo.
    Yes, the problem with CAIRIM was totally right. Unfortunately, I just initialized the Batch Link Feature and not the whole product. So, thank You very much for or Your help, Michael!

     

    Now, Timo's colleagues signed that they have a new problem with this user interface, it looks that when they wants to import the protsym file, they has got the following error message:

    And this one:

     

    Can You please help me that what could cause this kind of error message?

     

    Thank You so much in advance!

     

    Kind Regards,

    Ferenc Kornel Kelemen

    at IBM: ferenc.kornel.kelemen@hu.ibm.com



  • 4.  Re: CA InterTest don't work (CAVHCONF)

    Broadcom Employee
    Posted 08-22-2017 02:14 AM

    Dear Ferenc, 

     

    Thanks for opening the support case  yesterday as well! That was a good dicision. 
    As I wrote to you from the case last night - I assume that the Error4 occurs because a wrong port has been used. 
    If you specify the BLSPORT from CAVHUOPT in the GUI, it will appear as ‘Available’ but receive the Errro4 when trying to import a PROTSYM file. 
    A new requirement for the common server was to also specify a port that would be used to receive SYSPLEX debugging/scheduling requests in CAVHUOPT - but this port cannot be used for the GUI. 
    Instead you have to use the port specified in the CAVHDPLY job for the GUI. 

    And, you cannot use the same port as BLSPORT in CAVHUOPT and as PORT in the CAVHDPLY job - they must be different. 
    In some installations port 99999 cannot be used. We recommend to use a lower, free port number. 

     

    Can you please check and let me know whether it was helpful to resolve the error? 

     

    Thank you and best regards, 
    Ralf Guertler 
    CA Technologies 
    Sr Support Engineer 
    CA Testing Tools and CA Easytrieve Subject Matter Expert (SME) 



  • 5.  Re: CA InterTest don't work (CAVHCONF)

    Posted 08-24-2017 02:15 PM

    Hi,

    Thank you for your answer. 

    In my case problem was in wrong port number.

    I got new one from system programmer.

    It worked and I now can set breakpoints, watch data and so on.

    We have now next problem in debuging the program.

    We can send JCL but every control actions are offline.

    It looks that problem in is installation/conficuration.

    System programmers works to find the error.

    Br. Timo Mäenpää



  • 6.  Re: CA InterTest don't work (CAVHCONF)

    Broadcom Employee
    Posted 08-24-2017 06:18 PM

    Hi Timo, 

    Thank you for the status update that the port number resolved the initial  problem you encountered. I can see that you systems programmer is working with the Intertest support team case number 823163. Our support team will continue working with you SYSPROG through our problem tracking system to resolve any problems you encounter during your testing. 

    Regards, Bill