Topic
2 replies Latest Post - ‏2013-03-07T02:59:30Z by bluejoni2306
bluejoni2306
bluejoni2306
19 Posts
ACCEPTED ANSWER

Pinned topic Cics Explorer Debug tool plug in (testing batch) recieving error

‏2013-03-05T20:09:28Z |
Cics Explorer Debug tool plug in (testing batch) recieving error "Configuration not found". "Unable to launch default configuration".

Could anyone explain this to me. I have attach the actual message and job output in a file.
Updated on 2013-03-07T02:59:30Z at 2013-03-07T02:59:30Z by bluejoni2306
  • zdebug
    zdebug
    4 Posts
    ACCEPTED ANSWER

    Re: Cics Explorer Debug tool plug in (testing batch) recieving error

    ‏2013-03-06T11:00:06Z  in response to bluejoni2306
    Hi,
    I'm not sure why you see the default launch configuration not found message. What action prompted caused that to popup? I think CICS Explorer doesn't have Debug Configurations unlike RDz and wonder why you're seeing a message regarding launch configurations.

    Regarding the following messages, it seems like the connection was either refused or reset. Are we dealing with VMware setu and Debug Tool communicating to VM image(s)? Could it be possible that you're unable to ping 10.139.142.218 from your (host) TSO session?

    Try ping 10.139.142.218 from ISPF and that should work since Debug Tool initiates a connection from the host down to the workstation and if the workstation is unreachable (firewall or wrong TCP/IP address), you'd need to correct the issue. Talking about wrong or misspelt values in the TEST runtime string, I'm assuming you deliberately changed the (default) port from 8001 to 9001 as seen below.

    12.03.20 JOB13508 +EQA9999W - IP: 10.139.142.218
    12.03.20 JOB13508 +EQA9999W - Port: 9001
    12.03.20 JOB13508 +EQA9999W - UserId: TSSJM TaskNum: N/A

    Let us know how that works out.

    Cheers,
    zdebug
  • bluejoni2306
    bluejoni2306
    19 Posts
    ACCEPTED ANSWER

    Re: Cics Explorer Debug tool plug in (testing batch) recieving error

    ‏2013-03-07T02:59:30Z  in response to bluejoni2306
    I have managed to resolve this.
    The wrong Debug tool plug in was installe so uninstalled and reinstalled. Then had issues with LPEX editor being different version, so removed both Fault Analyser and Debug tool plug in and reinstalled both from my archived production downloads. I think an automatic update must have updated one of them to an incorrect level. So have removed automatic updates for now.