Topic
  • 11 replies
  • Latest Post - ‏2010-08-11T13:17:36Z by markevans
SystemAdmin
SystemAdmin
6195 Posts

Pinned topic Mainframe in Dallas 192.195.29.60 obsolete?

‏2010-06-04T16:58:55Z |

Hello,
I'm working with Jons ppt tutorial to get familiar with egl and the rbd. On slide 605 I should check the tcp-connection to the mainframe in Dallas, i.e. to 192.195.29.60.
I'm living in Germany and tried a ping with the result down here. Shouldn't this mainframe be accessible from Germany? Why it isn't? Is this IP address obsolete?
kind regards
Andreas Gronert
C:\Users\Andreas Gronert>ping 192.195.29.60
Ping wird ausgeführt für 192.195.29.60 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Ping-Statistik für 192.195.29.60:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),
Updated on 2010-08-11T13:17:36Z at 2010-08-11T13:17:36Z by markevans
  • markevans
    markevans
    3034 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-06-11T21:17:05Z  

    Andreas,
    Sorry to take so long to answer this one.
    You may still be able to use this. Some of these ip addresses are not setup to respond to a ping.
    Another address you might want to try if this one does not work is:
    192.84.47.60
    take care.

  • SystemAdmin
    SystemAdmin
    6195 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-06-16T16:01:54Z  
    • markevans
    • ‏2010-06-11T21:17:05Z

    Andreas,
    Sorry to take so long to answer this one.
    You may still be able to use this. Some of these ip addresses are not setup to respond to a ping.
    Another address you might want to try if this one does not work is:
    192.84.47.60
    take care.

    Hello Mark,
    thank you for your answer. I've tried a ping to 192.84.47.60 without success as well.

    If the server doesn't answer my ping, how could I confirm the accessibility of the server? Is there another way?
    kind regards
    Andreas Gronert
  • markevans
    markevans
    3034 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-06-16T18:41:09Z  
    Hello Mark,
    thank you for your answer. I've tried a ping to 192.84.47.60 without success as well.

    If the server doesn't answer my ping, how could I confirm the accessibility of the server? Is there another way?
    kind regards
    Andreas Gronert

    Andreas,
    Since they have not enabled Ping, you will just have to try the call and see what happens. If the CICS region is accesible using one of those addresses, then the ability to do a ping will not matter.

  • SystemAdmin
    SystemAdmin
    6195 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-06-30T07:19:14Z  
    • markevans
    • ‏2010-06-16T18:41:09Z

    Andreas,
    Since they have not enabled Ping, you will just have to try the call and see what happens. If the CICS region is accesible using one of those addresses, then the ability to do a ping will not matter.

    Hello Mark,
    thank you for your advice up to now. I'Ve followed the "Lab - Big Picture and Steps" where to call the remote Cobol program at the mainfraim in Dallas. When clicking the button to execute the respective remote Cobol program I'm getting an error message in my console view like shown below.

    What could be the reason? Let me know if you need any protocols etc. for analyzing this problem or if you even would like to analyze the problem in a remote session on my workstation.
    kind regards
    Andreas Gronert

    6/30/10 9:25:37:562 CEST 0000001d ApplicationMg A WSVR0221I: Application started: EGLWebEAR
    6/30/10 9:25:37:562 CEST 0000001d CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=EGLWebEAR in BLA WebSphere:blaname=EGLWebEAR started.
    6/30/10 9:29:50:390 CEST 0000002c servlet I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: EGLWebEAR [/EGLWeb] [/callCBL.jsp]: Initialization successful.
    6/30/10 9:33:36:609 CEST 0000002c ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source.
    6/30/10 9:33:36:609 CEST 0000002c ConnectionEve A J2CA0216I: The Connection Manager received a fatal connection error from the Resource Adapter for resource eis/eglcics. Information may be available in previous messages or exceptions.
    6/30/10 9:33:53:593 CEST 0000002d ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source.
    6/30/10 9:33:53:593 CEST 0000002d ConnectionEve A J2CA0216I: The Connection Manager received a fatal connection error from the Resource Adapter for resource eis/eglcics. Information may be available in previous messages or exceptions.
    6/30/10 9:33:53:609 CEST 0000002d SystemOut O EGL0124E An error occurred during an attempt to communicate with CICS. Exception is CTG9630E IOException occurred in communication with CICS
    EGL0002I The error occurred in callCBL processing the callCBLCLSP2 function.
    6/30/10 9:33:53:609 CEST 0000002c SystemOut O EGL0124E An error occurred during an attempt to communicate with CICS. Exception is CTG9630E IOException occurred in communication with CICS
    EGL0002I The error occurred in callCBL processing the callCBLCLSP2 function.
  • markevans
    markevans
    3034 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-06-30T12:03:31Z  
    Hello Mark,
    thank you for your advice up to now. I'Ve followed the "Lab - Big Picture and Steps" where to call the remote Cobol program at the mainfraim in Dallas. When clicking the button to execute the respective remote Cobol program I'm getting an error message in my console view like shown below.

    What could be the reason? Let me know if you need any protocols etc. for analyzing this problem or if you even would like to analyze the problem in a remote session on my workstation.
    kind regards
    Andreas Gronert

    6/30/10 9:25:37:562 CEST 0000001d ApplicationMg A WSVR0221I: Application started: EGLWebEAR
    6/30/10 9:25:37:562 CEST 0000001d CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=EGLWebEAR in BLA WebSphere:blaname=EGLWebEAR started.
    6/30/10 9:29:50:390 CEST 0000002c servlet I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: EGLWebEAR [/EGLWeb] [/callCBL.jsp]: Initialization successful.
    6/30/10 9:33:36:609 CEST 0000002c ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source.
    6/30/10 9:33:36:609 CEST 0000002c ConnectionEve A J2CA0216I: The Connection Manager received a fatal connection error from the Resource Adapter for resource eis/eglcics. Information may be available in previous messages or exceptions.
    6/30/10 9:33:53:593 CEST 0000002d ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source.
    6/30/10 9:33:53:593 CEST 0000002d ConnectionEve A J2CA0216I: The Connection Manager received a fatal connection error from the Resource Adapter for resource eis/eglcics. Information may be available in previous messages or exceptions.
    6/30/10 9:33:53:609 CEST 0000002d SystemOut O EGL0124E An error occurred during an attempt to communicate with CICS. Exception is CTG9630E IOException occurred in communication with CICS
    EGL0002I The error occurred in callCBL processing the callCBLCLSP2 function.
    6/30/10 9:33:53:609 CEST 0000002c SystemOut O EGL0124E An error occurred during an attempt to communicate with CICS. Exception is CTG9630E IOException occurred in communication with CICS
    EGL0002I The error occurred in callCBL processing the callCBLCLSP2 function.

    Andreas,
    I know there have been changes on the Dallas system and it could be that these IP addresses are no longer valid or require SSL (encrypted) communicaitons now. It also could be that the CICS region is down as we do not monitor this on any kind of daily basis.
    I will have to check at some point if something has changed since these tutorials were done (I know this section is older)....
    Thanks for bringing it to our attention.

  • markevans
    markevans
    3034 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-07-28T12:27:53Z  
    • markevans
    • ‏2010-06-30T12:03:31Z

    Andreas,
    I know there have been changes on the Dallas system and it could be that these IP addresses are no longer valid or require SSL (encrypted) communicaitons now. It also could be that the CICS region is down as we do not monitor this on any kind of daily basis.
    I will have to check at some point if something has changed since these tutorials were done (I know this section is older)....
    Thanks for bringing it to our attention.


    Andreas,
    Sorry to take so long to answer this. Don't know if you still need it, but the IP address has changed to
    192.84.47.60
    I ran it last week and it worked for me.
    take care.

  • SystemAdmin
    SystemAdmin
    6195 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-07-30T14:29:38Z  
    • markevans
    • ‏2010-07-28T12:27:53Z

    Andreas,
    Sorry to take so long to answer this. Don't know if you still need it, but the IP address has changed to
    192.84.47.60
    I ran it last week and it worked for me.
    take care.

    Hello Mark,
    according to the tutorial and your message about the changed ip, I have set the following:

    TPNName: CPMI
    ConnectionURL: tcp://192.84.47.60
    ServerName: CICSACB3
    PortNumber: 2006

    As I think the server name should have changed also, I also tried to leave the server name free or set it to the given IP-Address but nothing was working.

    Could you please give me all values to set for the connection at my WAS properly. Could you further write to me if I need to restart the server, republish or just save it, afer changing any value?
    kind regards
    Andreas Gronert
  • markevans
    markevans
    3034 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-08-08T23:07:21Z  
    Hello Mark,
    according to the tutorial and your message about the changed ip, I have set the following:

    TPNName: CPMI
    ConnectionURL: tcp://192.84.47.60
    ServerName: CICSACB3
    PortNumber: 2006

    As I think the server name should have changed also, I also tried to leave the server name free or set it to the given IP-Address but nothing was working.

    Could you please give me all values to set for the connection at my WAS properly. Could you further write to me if I need to restart the server, republish or just save it, afer changing any value?
    kind regards
    Andreas Gronert

    Andreas,
    That should be correct. I did not use the CICSJ2C connection as described in the tutorial, but a CICSECI call (i.e. direct).
    I used CICSACB3 as the region name (i.e. server name).
    You would need to recycle WAS after changing the values.
    Do you have any error messages now that you are using the new TCPIP address? Did they change?
    It also could be a point in time issue if they happen to be doing maintenance and have some jobs down (CICS or CTG).
    Anyway, let me know what you find out.

  • markevans
    markevans
    3034 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-08-09T18:27:24Z  
    • markevans
    • ‏2010-08-08T23:07:21Z

    Andreas,
    That should be correct. I did not use the CICSJ2C connection as described in the tutorial, but a CICSECI call (i.e. direct).
    I used CICSACB3 as the region name (i.e. server name).
    You would need to recycle WAS after changing the values.
    Do you have any error messages now that you are using the new TCPIP address? Did they change?
    It also could be a point in time issue if they happen to be doing maintenance and have some jobs down (CICS or CTG).
    Anyway, let me know what you find out.


    Andreas,
    I tried this today with a CICSJ2C connection and things worked fine.
    Attached is the word document with my settings.


    Attachments:
    remoteCall.doc
    Updated on 2010-08-09T18:27:24Z at 2010-08-09T18:27:24Z by markevans
  • SystemAdmin
    SystemAdmin
    6195 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-08-11T12:58:17Z  
    • markevans
    • ‏2010-08-09T18:27:23Z

    Andreas,
    I tried this today with a CICSJ2C connection and things worked fine.
    Attached is the word document with my settings.


    Attachments:
    remoteCall.doc
    Hello Mark,
    today I did try again, without any changes since last time, when it didn't work but today it was working.

    I've also appended screenshots with my settings from the WAS and the build descripter which are marginal differerent from yours for all egl userers that are interestet in the solution.

    Thank you very much.
    kind regrds
    Andreas Gronert
    Attachments:
    remoteCall.doc
    Updated on 2010-08-11T12:58:17Z at 2010-08-11T12:58:17Z by SystemAdmin
  • markevans
    markevans
    3034 Posts

    Re: Mainframe in Dallas 192.195.29.60 obsolete?

    ‏2010-08-11T13:17:36Z  
    Hello Mark,
    today I did try again, without any changes since last time, when it didn't work but today it was working.

    I've also appended screenshots with my settings from the WAS and the build descripter which are marginal differerent from yours for all egl userers that are interestet in the solution.

    Thank you very much.
    kind regrds
    Andreas Gronert
    Attachments:
    remoteCall.doc

    Andreas,
    Glad you got it to work finally.
    If I saw things correctly, the only change you made was to remove the ServerName from the custom properties. I am very surprised you got it to work without specifying a ServerName as this is how CTG on the host knows what region to direct the request to. Maybe they only have one...but I did not see any place this was specified.
    But again..glad you got it working.