RE: ROI credit card software upgrade problems

["Yuriy Veletnik" <YVeletnik@xxxxxxxxxx>]

Our is is set to *remote and ROI works fine 

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Peter Dow
Sent: Tuesday, May 19, 2009 3:41 PM
To: Java Programming on and around the iSeries / AS400
Subject: Re: ROI credit card software upgrade problems

Hi Neill,

Well, they got a unsatisfying answer from IBM.  the HOSTSCHPTY parm on
the CHGTCPDMN command was set to *REMOTE; when they changed it to
*LOCAL, ROI's software worked.

What's unsatisfying is that the CHGTCPDMN command logs its use in QHST,
and there was no use of it from 05/12 - 05/19 other than the change a
few minutes ago to set the host search to *LOCAL, and from an IPL late
yesterday while attempting to fix the problem.  That's another mystery
-- why does an IPL do a CHGTCPDMN?  That command is not in their startup
program.

Anyway, tonight they'll be doing another IPL for the latest PTFs, and
after that, while no one is on, we'll test it by setting HOSTSCHPTY to
*REMOTE and seeing if the problem reoccurs.  If it is indeed the
problem, the question becomes how did it get changed without leaving any
trace in QHST?

Btw, file QATOCTCPIP in QUSRSYS contains the TCP/IP configuration data,
and unfortunately, we didn't know that soon enough to check the objects
change date/time.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /




Neill Harper wrote:
> I know this is a boring answer, but has anybody been tinkering with 
> firewalls or any kind of new server etc?
>
> Is there anything in any of the joblogs on the server jobs?
>
> Neill
>
> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx 
> [mailto:java400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Joe Sam Shirah
> Sent: 19 May 2009 19:09
> To: Java Programming on and around the iSeries / AS400
> Subject: Re: ROI credit card software upgrade problems
>
>
>     Hi Peter,
>
>     I often use Squirrel to hit various databases, and ran into 
> something similar to this:
>
>   
> > java.net.SocketTimeoutException: connect timed out
> >     
>
> with later JTOpen versions.  The issue there was that, by default, 
> Squirrel tries to open all schemas (read libraries or collections on 
> the AS/400) in the database at first connect.  When I turned off that 
> behavior, the problem
>
> went away.
>
>     I checked the JDBC properties, but couldn't find anything 
> regarding timeouts.  Since my change worked, and I never saw the issue

> in my programs using the driver, I didn't pursue it further.  My 
> suspicion, however, is that JTOpen now does something different with 
> socket connections that allows
>
> the timeout, and there may be a more or less undocumented (in JTOpen) 
> socket
>
> setting it uses.
>
>         So I'm wondering if the upgrade attempts to check all schemas 
> when it starts up.  Was the initial problem the same or do they have 
> the log for that?
>
>     I see your site doesn't claim any Java skills and Visual Basic 
> probably won't help, so you may want to contact someone familar with 
> Java if you need
>
> to dig deeper.  I also would encourage your client to set some fires 
> under ROI's support staff; doesn't sound like a good ROI here...
>
>     HTH,
>
>
>                                                          Joe Sam
>
> Joe Sam Shirah -        http://www.conceptgo.com
> conceptGO       -        Consulting/Development/Outsourcing
> Java Filter Forum:       http://www.ibm.com/developerworks/java/
> Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
> Going International?    http://www.jguru.com/faq/I18N
> Que Java400?            http://www.jguru.com/faq/Java400
>
> ----- Original Message -----
> From: "Peter Dow" <maillist@xxxxxxxxxxxxxxx>
> To: <java400-l@xxxxxxxxxxxx>
> Sent: Tuesday, May 19, 2009 12:53 PM
> Subject: ROI credit card software upgrade problems
>
>
>   
> > Hi Everyone,
> >
> > A customer of mine who uses ROI's credit card authorization software 
> > (mostly in Java) ran into a problem. On Thursday, 05/14/2009, they 
> > restarted the server and it started up just fine.  On Sunday, 
> > 05/17/2009, they tried to restart the server and it failed.
> >
> > ROI couldn't determine anything immediately, and asked them to 
> > upgrade to the latest version before continuing.  So they upgraded.  
> > The upgrade tries to run a couple of AS400 commands (from Java) and 
> > fails.  Here's the upgrade log:
> >
> > 2009-05-18 21:42:22,105
> > *********************************************************************
> > *
> > 2009-05-18 21:42:22,146 JCharge upgrade to version
> > 7.4.3.14
> > 2009-05-18 21:42:22,146 JCUpgrade launched with no command line 
> > arguments.
> > 2009-05-18 21:42:22,152
> > Initializing...
> > 2009-05-18 21:42:22,225
> > ok
> > 2009-05-18 21:42:22,225 Connecting to services...
> > 2009-05-18 21:42:26,998
> > ok
> > 2009-05-18 21:42:26,998 Checking for dependent logical files in other

> > libraries...
> > 2009-05-18 21:42:26,998 DSPDBR FILE(ASCCOM1/*ALL) OUTPUT(*OUTFILE)
> > OUTFILE(ASCCOM1/DSPDBR)
> > 2009-05-18 21:45:37,275 java.net.SocketTimeoutException: connect 
> > timed out
> > 2009-05-18 21:45:37,384   at
> > java.lang.Throwable.<init>(Throwable.java:195)
> > 2009-05-18 21:45:37,384   at
> > java.lang.Exception.<init>(Exception.java:41)
> > 2009-05-18 21:45:37,384   at
> > java.io.IOException.<init>(IOException.java:40)
> > 2009-05-18 21:45:37,384   at
java.net.SocketTimeoutException.<init>(SocketTimeoutException.java:24)
> > 2009-05-18 21:45:37,384   at
> > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
> > 2009-05-18 21:45:37,384   at
> > java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
> > 2009-05-18 21:45:37,385   at
> > java.net.Socket.connect(Socket.java:488)
> > 2009-05-18 21:45:37,385   at
> > java.net.Socket.connect(Socket.java:438)
> > 2009-05-18 21:45:37,385   at
> > java.net.Socket.<init>(Socket.java:148)
> >
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.PortMapper.getServerSocket(PortMapper.java:141)
> >
> > 2009-05-18 21:45:37,385   at
> >
> >     
> com.ibm.as400.access.AS400ImplRemote.signonConnect(AS400ImplRemote.jav
> a:1855
> )
>   
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.AS400ImplRemote.signon(AS400ImplRemote.java:1755
> > )
> >
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.AS400.sendSignonRequest(AS400.java:2571)
> >
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.AS400.promptSignon(AS400.java:2157)
> >
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.AS400.signon(AS400.java:3412)
> >
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.CommandCall.chooseImpl(CommandCall.java:238)
> >
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.CommandCall.run(CommandCall.java:571)
> >
> > 2009-05-18 21:45:37,385   at
> > com.ibm.as400.access.CommandCall.run(CommandCall.java:610)
> >
> > 2009-05-18 21:45:37,386   at
> > JCUpgrade.runCommand400(JCUpgrade.java:549)
> >
> > 2009-05-18 21:45:37,386   at
> > JCUpgrade.checkLogicalFiles(JCUpgrade.java:107)
> >
> > 2009-05-18 21:45:37,386   at
> > JCUpgrade.execute(JCUpgrade.java:79)
> >
> > 2009-05-18 21:45:37,386   at
> > JCUpgrade.main(JCUpgrade.java:66)
> >
> > 2009-05-18 21:45:37,386 Error: see log file for details
> >
> > It appears to be trying to do a remote signon and timing out.  All 
> > the host servers are started, so why is it timing out? Or is it some 
> > other problem?
> >
> > tia,
> > *Peter Dow* /
> > Dow Software Services, Inc.
> > 909 793-9050
> > pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /
> >
> >     
>
>   

--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.

Your email was stripped of active html components for safety.