Topic
5 replies Latest Post - ‏2013-01-23T10:21:17Z by SystemAdmin
ENO2010
ENO2010
45 Posts
ACCEPTED ANSWER

Pinned topic [RDZ 8.5.1] : Debug

‏2013-01-22T09:35:53Z |
Hi,
I would like to use the debugger for my batch COBOL program but every time I ran the jcl I received the next error :

14.24.20 JOB00675  +EQA9999E - Debug Tool TCPIP error 14.24.20 JOB00675  +EQA9999E - FeName=EQACSMTP Loc=110 Func=CONNEC Rc=-1       Fc=60 14.24.20 JOB00675  +EQA9999E - Err: ETIMEDOUT       Connection timed out 14.24.20 JOB00675  +EQA9999E - IP: 192.168.0.42 14.24.20 JOB00675  +EQA9999E - Port:  8001 14.24.20 JOB00675  +EQA9999E - UserId: EMPOT01  TaskNum: N/A 14.24.20 JOB00675  +Communications Failure allocating session. 14.24.20 JOB00675  +EQA9999E - Debug Tool TCPIP error 14.24.20 JOB00675  +EQA9999E - FeName=EQACSMTP Loc=230 Func=SHUTDO Rc=-1       Fc=60 14.24.20 JOB00675  +EQA9999E - Err: ETIMEDOUT       Connection timed out 14.24.20 JOB00675  +EQA9999E - IP: 192.168.0.42 14.24.20 JOB00675  +EQA9999E - Port:  8001 14.24.20 JOB00675  +EQA9999E - UserId: EMPOT01  TaskNum: N/A 14.24.20 JOB00675  IEF404I EMPOT051 - ENDED - TIME=14.24.20 14.24.20 JOB00675  $HASP395 EMPOT051 ENDED


here is my jcl


//EMPOT011 JOB , 
// MSGCLASS=H,MSGLEVEL=(1,1),TIME=(,4),REGION=144M,COND=(16,LT) 
//GO    EXEC   PROC=ELAXFGO,GO=C2F, 
//             LOADDSN=EMPOT05.HOG.LOAD, 
// PARM.RUN=('/TEST(,,,TCPIP&192.168.0.42%8001:*)') 
// 
//*


on my workstation, I add the port 8001 to the firewall
How can I now on why port the debug tool on Z/os in listening?

regards

Eric
Updated on 2013-01-23T10:21:17Z at 2013-01-23T10:21:17Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    1086 Posts
    ACCEPTED ANSWER

    Re: [RDZ 8.5.1] : Debug

    ‏2013-01-22T10:25:05Z  in response to ENO2010
    Hope you have compiled your programs with debug compiler options. If not, you can refer the link below to get the set-up details.

    https://www.ibm.com/developerworks/mydeveloperworks/wikis/form/anonymous/api/library/3f18af90-d768-47d5-85f2-c78c0b244ecb/document/922b106b-174a-4817-a02e-362d6ff7cbf7/attachment/afc1c784-e59f-4b2c-ae9e-ccc1a1e25a21/media/RDz%20Workbench%20-%20Debugging%20zOS%20COBOL.ppt
    • ENO2010
      ENO2010
      45 Posts
      ACCEPTED ANSWER

      Re: [RDZ 8.5.1] : Debug

      ‏2013-01-22T12:46:42Z  in response to SystemAdmin
      I solved my problem it was an issue with my virtual machine.
      Now I can debug my program but I didn't add any param for the compilation.

      here is the jcl for compile/link
      
      
      //EMPOT051 JOB , 
      // MSGCLASS=H,MSGLEVEL=(1,1),TIME=(,4),REGION=144M,COND=(16,LT) 
      //* 
      //STP0000 EXEC PROC=ELAXFCOC, 
      // CICS=, 
      // DB2=, 
      // COMP= 
      //COBOL.SYSPRINT DD DISP=SHR, 
      //        DSN=EMPOT05.HOG.LISTING(C2F) 
      //COBOL.SYSDEBUG DD DISP=SHR, 
      //        DSN=EMPOT05.HOG.SYSDEBUG(C2F) 
      //COBOL.SYSLIN DD DISP=SHR, 
      //        DSN=EMPOT05.HOG.OBJ(C2F) 
      //COBOL.SYSLIB DD DISP=SHR, 
      //        DSN=EMPOT05.HOG.COPY 
      //COBOL.SYSXMLSD DD DUMMY 
      //COBOL.SYSIN DD DISP=SHR, 
      //        DSN=EMPOT05.HOG.COBOL(C2F) 
      //* 
      //******* ADDITIONAL JCL FOR COMPILE HERE ****** 
      //LKED EXEC PROC=ELAXFLNK 
      //LINK.SYSLIB DD DSN=CEE.SCEELKED, 
      //            DISP=SHR 
      //LINK.OBJ0000 DD DISP=SHR, 
      //        DSN=EMPOT05.HOG.OBJ(C2F) 
      //LINK.SYSLIN DD * INCLUDE OBJ0000 
      /* //LINK.SYSLMOD   DD  DISP=SHR, //        DSN=EMPOT05.HOG.LOAD(C2F) //* /
      /******* ADDITIONAL JCL FOR LINK HERE ******
      


      and here the debug jcl

      
      
      //EMPOT011 JOB , 
      // MSGCLASS=H,MSGLEVEL=(1,1),TIME=(,4),REGION=144M,COND=(16,LT) 
      //GO    EXEC   PROC=ELAXFGO,GO=C2F, 
      //           LOADDSN=EMPOT05.HOG.LOAD, 
      // PARM.RUN=('/TEST(,,,TCPIP&myIpAdres:8001:*)') 
      // 
      //*
      


      Do you what are the goals of the parameters show in the ppt?

      Eric
      • SystemAdmin
        SystemAdmin
        1086 Posts
        ACCEPTED ANSWER

        Re: [RDZ 8.5.1] : Debug

        ‏2013-01-23T10:21:17Z  in response to ENO2010
        The TEST option is required for remote debugging. It produces symbol and statement information that enables the debugger to perform symbolic source-level debugging
  • SystemAdmin
    SystemAdmin
    1086 Posts
    ACCEPTED ANSWER

    Re: [RDZ 8.5.1] : Debug

    ‏2013-01-22T10:41:20Z  in response to ENO2010
    Have you checked in the Debug perspective that you have port 8001 listening?
    In Debug pane under debug perspective there is an icon showing the status (listening on port/not listening).
  • SystemAdmin
    SystemAdmin
    1086 Posts
    ACCEPTED ANSWER

    Re: [RDZ 8.5.1] : Debug

    ‏2013-01-22T14:39:40Z  in response to ENO2010
    Happy to hear that you resolved the problem.

    I just want to add a couple of suggestions when dealing with connection problems.

    1) The direction of the connection is from the host to the workstation running RDz
    ** this means that the workstation must be visible to the host.
    ** a simple test is to ping the workstation from the host
    2) Try a different port. The default is 8001 but you can enter any valid and available port number
    ** you can even enter a port range (8001-8005) or port list (8001,8003) and RDz will attempt each port number in the range until it finds one that is available. If you use a range then hover on the debug daemon icon to determine which port is being used.
    ** I have seen cases where port 8001 is blocked outbound on host machines when using VPN.
    3) When using VPN point Debug Tool to the ip address assigned to the VPN session. Not the ip address of your workstation.
    ** The debug daemon has a drop down menu (arrow beside the icon) and one of the actions is to display the ip addresses of the workstation. IP addresses that begin with 198.162.x.x are normally locally assigned and are not visible to the host. Use ping from the host to determine if the ip address is visible.
    ** the drop down action will show VPN assigned addresses.