3270 Emu program keep alive setup cause 7507(TN3270 Server) Down

Hi
need all of your suggest
my cx use 3270 Emu program which enable keep alive 30 second in it's default config
when client idle 30 second,it auto triger keepalive to TN3270 server(7507)
But 7507 send back TN_DEV_IN use(TN device in use)to client,and client must reconnect to server
does any one know how to bypass 7507 send this to client,
my cx have exceed four hundred 3270 client
it takes so long to set per client
so any command can issue in 7507 to bypass this
tks

I don't know if these commands will bypass the problem, only that they might. I'm really guessing here, because the result you describe doesn't add up. My guess is that your emulator is missing a timing-mark or no-op keepalive from the server, and when the client then sends it's own keepalive the server views it as a sequence error and closes the session. The best way to work this out is probably to start with a trace of a complete session.

Similar Messages

PPPoe Keep-Alive Program for Solaris 8?

Is there a PPPoE Keep-alive program for Solaris 8? I need this because my DSL provider keeps knocking me off and therefore I lose my connection. I would prefer the program be precompiled if there is one available.
-Thanks in advance

It sounds like you are accidentally running NIS. Somewhere, you told your system that "mydomain.net" was your NIS domain. Look to see if you have an /etc/defaultdomain file. Remove it. You don't have NIS, and you probably have the wrong /etc/nsswitch.conf setup then, too.
Try copying /etc/nsswitch.dns /etc/nsswitch.conf (make a backup first).
Verify that you have 'nameserver' entries in /etc/resolv.conf and a 'domain mydomain.net' entry at the very beginning. This is where you let the system know your Internet domain (well, also in the fully-qualified domain name of your machine in your /etc/hosts file).
In your /etc/hosts file, the first name of your machine should be the FQDN, then a short alias, if you are going to use one, and probably "loghost". You might put "loghost" as an alias for "localhost".
Make sure your 'hostname' reflects the FQDN, or mail might not like it. Try setting the hostname with 'uname -S <hostname>' if it isn't correct.
Good luck.

Installer setup program keeps running How to shut it off

Printer is working. Installer Setup program keeps coming up on desktop with a spinning disc. How to shut it off?

Apple Menu / System Preferences / Bluetooth.
Make sure the box next to "Show Bluetooth status in the menu bar" is not checked.

Nexus 7000 - Moving vPC keep alive

We have two Nexus 7010 switches running a vPC domain between the two switches. On one of the 7010B, the peer keep alive (from the mgmt VRF) is connected to a 3560B *and* that 3560B also has a data connection back to the same 7010B. Everything is fine with that setup.
Our second 7010A, the peer keep alive link is also connected to a coresponding 3560A switch. However, that 3560A switch is not connected to 7010A.
I want to move the uplink from the 3560A from where it is to the 7010A which will break the keep alive. However, I will not be breaking the vPC peer link as it is a pair of 10G connections between the two 7010 switches.
I have read that the vPC won't come up unless the peer keep alive is present, but it wasn't clear about taking down the keep alive link momentarily. Moving the cable would be quick, but I know the mac table will need to update since 7010B switch will now see the keep alive across it's peer link instead of some other direction.
Can I take the peer keep alive link down providing the peer link stays up?
We are running kickstart and system version 5.0(3).
Thanks!
/alan

Peer keepalive works on UDP port 3200 over IP with 1 sec interval and 5 sec timeout.
Iit is not requirement to have peer-keepalive destination IP in same subnet but if you do not have it in same subnet then you need to make sure you route it properly and your IP routed infrastructure that carries keeplive satisfies above requirement to make sure not a single event cause on that IP infrastructure causes keeplives to loose packets since peer-keepalive is UDP it is not reliable delivery method.
Recommendation in past i heard was to use your managemet ports as peer-keepalive. But one problem happens during ISSU with dual sup, the each supervisor reboots and after it comes up role of active and standby gets switch at the end. So If you did not connect two managment ports(one from each supervisor) to your management network then you will loose keepalives during software upgrade because supervisor switch over occurs and new maangement port becomes active.
So second recomendation is to create one peer-keepalive vrf so that it will have its own address space, if you have M1 1 gig card in each switch then connect one cable between switch and assign IP address (like 1.1.1.1-2/30) and put it in peer-keepalive vrf. With this set up during ISSU you do not loose peer keepalives because line cards does not need to reboot and your peer-keepalive UDP traffic will not depend on any other switch or router.

Mail program keeps re-asking for password for my Yahoo Mail

So I use the mail program on my macmini (running 10.7.5). After I've setup my yahoo mail (and it has initially accepted the password) it keeps wanting to have me re-enter the password: Message says:
"The Yahoo! IMAP server “imap.mail.yahoo.com” rejected the password for user “[email protected]” Enter your password again or cancel. "
Then I re-enter the password each time (which is accepted) and then 5 minutes later it prompts me to re-enter all over again!
Help! -- And keep it simple, cause I'm a computer neophyte. Thanks

Hi John,
Could you have more than one entry for imap.mail.yahoo.com in Keychain Access?
Open Keychain Access in Utilities, use Keychain First Aid under the Window Menu item, then either check the Password under that item, change it, or delete it and start over.
Then See if this helps...
Mac OS X 10.4 Help, I forgot a password in my Keychain
http://docs.info.apple.com/article.html?path=Mac/10.4/en/mh1960.html
Resetting your keychain in Mac OS X...
If Keychain First Aid finds an issue that it cannot repair, or if you do not know your keychain password, you may need to reset your keychain.
http://support.apple.com/kb/TS1544

WRT54G v 7.0 -- Setting "Keep Alive: Redial Period" not correct (radio button)

Hi,
I own a Linksys-Router WRT54G v7.0 with firmware v7.00.8 build 008, Jul. 9, 2009.
On the web GUI (Setup/Basic Setup) there's a setting "Keep Alive: Redial Period XX Sec.". As I'd like to stay connected with my provider permanently, I've set the radio button to "Keep Alive: Redial Period" and the according text field to "30" seconds. Then, I've clicked "Save Settings" and got a confirmation message that the settings got saved.
Anyway, even after saving the settings the according radio button is still set to "Connect on Demand...". But that is only true for newer browsers, like e.g. IE8, IE7 or Firefox 8. If you use an older browser, like e.g. IE6, then the radio button is correctly set to "Keep Alive: Redial Period" with a value of "30" seconds.
Conclusion: The settings get correctly saved by the router (I can confirm that), but they don't get correctly shown in the web GUI. Looks like a HTML/Javascript bug in the router's admin web GUI. That's really annoying as you never exactly know the effective settings...
Can someone confirm that bug? Is there a newer firmware than version 7.00.8?
Regards,
Patrick

Try to clear the browser's cache as well.
"Don't fix it if it ain't broken."

How to Keep Alive a specific HFM application

My PRD landscape has 2-3 applications. Whenever any application loads for the first time in the memory, it takes quite some time before it is loaded. Once the application is loaded, the response times are pretty quick and acceptable.
During specific parts of the day / month, a specific application becomes active. During this time, other applications may or may not be used, but one specific application is definitely used. I want to keep this application's cubes loaded in the RAM, so that response times are quick, whenever the user needs it - whether for the first time or otherwise.
How to keep alive a specific application's cubes alive and loaded in RAM? I am not looking for general solution like setting the "FM Service" to Automatic (currently it is set Manual) - setting this to Automatic, will affect all applications. However, I am looking for a specific application at a specific period of time.
I am ok with a custom solution if required. Let me know, what are my options.

I think you are looking for an inappropriate solution to your problem. Most HFM applications take a few seconds to start up. If your application takes such a long time to start up you really need to examine the root cause. Start by removing the Sub NoInput and Sub Input routines in your rules to see if this is the reason the application takes so long to start.
If the removal of those routines does not significantly change the startup time, look through the event logs for possible causes. It is possible you have a connection problem with the Oracle database for example, or you have an environment configuration problem where the HFM application servers have a very slow connection to the database server, or possibly the database server performs poorly.
I strongly suggest you investigate these root casues first before trying to make HFM behave in a non-standard way. Certainly you can start the HFM Management Service, which will start all of your HFM applications and keep them all up and running. This approach does not allow the applications to shut down on their own though. Only use this if you have exchausted your investigations (as I suggsted above).
--Chris

Http keep-alive with SOAP webservices

Just had an interesting experience with a web service setup behind UAG...under low load conditions all SOAP responses were coming across with no issue...once a high load was introduced by the client app the behavior changed where an initial request was
processed and subsequent requests were rejected by UAG with a Bad Parameter : Length message...but high load (relatively) on a web browser ran without issue...the client app had to wait ~100 seconds before the next request would process correctly...browser
works - app has problems...turns out it was the keep-alive "default" settings on both the client app server, as well as my web service in IIS...so -apparently UAG thought the 2nd (and subsequent < 100 seconds) were a parameter of the first request...and
was way too long and got rejected...I unchecked the keep-alive enabled box on the http response header (set common headers) and all is fine now! Apparently the browsers were closing the connection with each page load and the service responded appropriately
- so it looked like all was well. Using SOAP UI revealed the error...but it also had it's connection set to keep-alive...once that was disabled in SOAP UI all requests ran correctly...that's when I poked around and found that response header setting.

ejp wrote:
and also an incorrect implementation of the timeout period. This code will still wait forever if no data arrives.You're right... actually I didn't mean to put that while loop there! What I meant was simply
if (!reader.ready())
wait(keepAliveTimeout);
if (!reader.ready())
break mainLoop;
// If we get here there is a new request to read...and I agree that it's ugly, that's why I'm asking you guys for help!
setSoTimeout() is of course a way to go... didn't think of that although I have kind of already added it to my code but with a different timeout. Thanks!
Last question then is:
does reader.readLine() block like reader.read(), or do I have to use the latter?
I would test for myself I could, but at the moment I can't...

Expense Report Export Program keeps on running normally for hours

Hi and assalam o alay kum Gurus
I am facing a problem in creating of invoice through expense report export program, I create expense report and run the program "Expense Report Export" but the issue is the program keeps on running for several hours we also raised SR for this issue but no solution provided after 6 months.
We are currently on R 12.1.2 can any one please guide me what to do, maybe any some one faced the same issue before, I really need your help just to check whether I missed any setup part or this is some kind of bug.
Best Regards
Danish.

Did you ever find a solution to this question? My internet expense templates are set to receipts are required for CASH and CREDIT CARD over a certain amount. Also, internet expense setup and admin is set to place the report on hold if receipt has not been received. I ran the Expense Report Export and they imported even though receipts were not received. Thank you.

URLConnection POST to external server requiring keep-alive fails because request is HTTP/1.0

          I have a class that when run as a "main" transmits a HTTP/1.1 post successfully
          to an external server. This external server requires keep-alive connections.
          However when instantiated inside a weblogic servlet container, the post fails
          because the HTTP protocol is set to HTTP/1.0. I have tried this with V5.1 SP11
          and then with V6.1 SP2 with the same result. The code works under Tomcat.
          I can find no way to force HTTP/1.1 in the URLConnection. Any suggestions?


Great. I have a question to BEA folks, if they ever read this newsgroup:
          what is the reason for installing WLS protocol handlers, and, if there is
          one, why the implementation is still buggy? I saw many, many instances when
          code making outgoing connections failed to work in WLS, and the solution is
          always the same - use handler which comes with the JVM.
          Bob Bowman <[email protected]> wrote:
          > <[email protected]> wrote:
          >>If it works as a standalone application and fails inside WebLogic, most
          >>likely this
          >>is caused by WebLogic http handler implementation. You can try to modify
          >>your code
          >>like this:
          >>
          >>URL url = new URL(null, "http://some_url", new sun.net.www.protocol.http.Handler());
          >>HttpURLConnection conn = (HttpURLConnection)url.openConnection();
          >>
          >>(you will need to modify weblogic.policy to allow your code to specify
          >>protocol
          >>handler).
          >>
          >>Bob Bowman <[email protected]> wrote:
          >>
          >>> I have a class that when run as a "main" transmits a HTTP/1.1 post
          >>successfully
          >>> to an external server. This external server requires keep-alive connections.
          >>> However when instantiated inside a weblogic servlet container, the
          >>post fails
          >>> because the HTTP protocol is set to HTTP/1.0. I have tried this with
          >>V5.1 SP11
          >>> and then with V6.1 SP2 with the same result. The code works under
          >>Tomcat.
          >>
          >>> I can find no way to force HTTP/1.1 in the URLConnection. Any suggestions?
          >>
          >>--
          >>Dimitri
          > Worked like a champ! Thanks.
          Dimitri

Weblogic shutting down keep-alive socket improperly?

We were sometimes experiencing strange IE behaviour when surfing on webapps on our Weblogic application servers. After investigation we found that IE has a bug in its resend behaviour, so when resending a POST request it sends the headers (including Content-Length) but forgets the form-data. This causes the server to time out waiting for the data. (Note: We are using Win2K and IE6 SP1 on the clients.)
The IE resend is triggered on a default installation when 31-59 seconds have passed since the last request.
This is because IE will try to reuse a socket that has been told to keep-alive until it has been idle for 60 seconds but WLS will by default close kept-alive sockets when they have been idle for 30 seconds. So in the range 31-59 seconds IE will consider the socket alive but WLS has closed it.
The resend bug is really an IE bug and doesn't concern WLS, but then I saw that IE would function correctly with an Apache server with a default keep-alive timeout of 15 seconds.
Using Ethereal I could get the information depicted in the tables below:
Weblogic with keep-alive timeout 30 secs
old socket
Time 00 : User navigates : IE POST request -> WLS, WLS HTML -> IE
Time 30 : Socket times out : (no network traffic)
Time 45 : User navigates : IE POST request -> WLS, WLS TCP_FIN -> IE
new socket
Time 45 : : IE resends POST request without form-data
Apache with keep-alive timeout 15 secs
old socket
Time 00 : User navigates : IE POST request -> Apache, Apache HTML -> IE
Time 15 : Socket times out : Apache TCP_FIN -> WLS
new socket
Time 45 : User navigates : IE POST request -> Apache, Apache HTML -> IE
To summarize, IE handles Apache well as Apache sends a TCP FIN telegram (to close the connection) as soon as the kept-alive socket times out.
Therefore IE never tries to reuse the socket but instead starts on a fresh one on the next navigation and a resend is never necessary.
Weblogic, on the other hand, doesn't send the TCP FIN (connection close) telegram until IE actually tries to use the connection even though it timed out 15 seconds earlier. In this case IE needs to resend the POST request and this is when the form-data is forgotten.
So, my question now is if WLS behaviour could be caused by not shutting down kept-alive sockets properly at keep-alive timeout? Or why are there no TCP FIN telegrams sent at timeout?
Mike Wilson

After doing some more investigation I have found that the "silent" shutdown of keep-alive sockets is only seen on the Linux version. The Windows version of Weblogic 8 behaves correctly, like Apache on Linux, but Weblogic on Linux does not...
Anyone can confirm if this is to be considered a bug?

LB configuration - Keep Alive.

I need to help configure proper load balancing between 2 building modules of Portal server.
SetUp:
Server A - Portal 1,Access Manager 1 , Directory 1
Server B - Portal 2, Access Manager 2, Directory 2
Logical Architecture.
-------- Server A
User Request -------------------->LB ------------>
------ Server B
I need to configure LB in a way that It has keep Alive info for Server A and B.I think there is a configuration required in some xml/property file so that If lets say server A goes down...the LB will automatically direct the next request to server B.
Can somebody point me in the right direction?
Thanks.

Do you need the SSO session created on Server A to failover to Server B or is it ok that the user has to reauthenticate if Server A goes down?
In any case you can either configure the LB for s.c. active cookie based persistence (LB is inserting it's own cookie) or s.c. passive cookie based persistence (LB is using a predefined cookie). I guess this is what you mean by 'keep-alive info' - correct?
Of course this does only work if no SSL is used or if SSL is terminated at the LB.
If SSL is used the only solution is to use client-IP based persistence.
All the above is only needed to prevent cross-talk between AM instances.
-Bernhard

GRE VPN & KEEP ALIVE

Dear all,
i am having problem with make keep alive connectivity all the time between 2 nodes.
I have A and B cisco routers established GRE VPN over ISP. Problem starts with when there are no active connection from host of A to host of B. It looks like VPN down. Another problem is when A 's having temp power outage and when power comes there is no active connection even WAN protocol is down.When reload A router manually then connection comes up.
I am thinking that maybe some configuation like keep alive retry something like that.
Do guys have any idea on this matter ?

GRE tunnels are usually used in combination with a dynamic routing protocol that keeps the tunnel up and active. If you are using static routes there is no traffic to keep the tunnels up when the applications are not transmitting.
You have two options:
1. Increase the isakmp/ipsec lifetimes.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_configuration_guide_chapter09186a00800d981f.html#1001095
2. Setup keepalives (Best Option)
crypto isakmp keepalive (Number of seconds between keep alives) (Number of seconds between retries if keepalive fails)

Workstation keep-alive and connectivity failure detection

Dear all,
I intend to automatically detect network failures from my workstation client and have it attempt to reconnect to the server on its own.
Browsing the documentation for related information I saw the keep-alive option. If I understood correctly you can have the workstation generate periodic keep-alive messages to the server and if these are not acknowledged, all subsequent ATMI calls will fail with TPESYSTEM.
My doubts regarding this are the following:
1) Is there some dummy ATMI function I can invoke periodically to check for a disconnection? Otherwise network failures might go by unnoticed if there are periods where my WSC doesn't require to communicate with the server.
2) Once I get a TPESYSTEM failure, is there some way to programatically discriminate if the cause is a network disconnection? It is a pretty generic error after all.
3) Once all ATMI functions start failing due to keep-alive detecting a network failure, can the system recover on its own? or must I reconnect to the server? What I mean is, maybe some keep alive messages where lost, the system passes to the 'disconnected' state, but then the K.A. messages keep being generated and upon correct acknowledgement of these, subsequent ATMI calls will stop failing.
4) Does the WSC go to 'disconnected' state after the first unanswered keep alive message? or is there some sort of tolerance like, say, 'If N messages in a row are not answered then assume the connection to be dead'.
I'm sorry if it was too long a post, but neither searching the documentation nor this forum clarified any of these issues for me.
Many thanks for your attention.
Regards.

Cacho,
1. I assume that you're talking about the WSL CLOPT option "-K
{client|handler|both|none}", which causes periodic keepalive messages to be
sent. When this option is used, there is no need for the WSC to perform any
periodic operations to keep the network connection alive.
However, if you are worried that the network might suffer a transient
failure and you want to perform your first ATMI call after an extended
period of inactivity as quickly as possible without waiting for another
tpinit(), you may want to perform periodic dummy operations so that you can
reissue the tpinit() if needed as soon as the network connection is
restored.
One option is to make a tpcall() to the ".TMIB" service with an FML32 buffer
where TA_OPERATION is set to "GET" and the other fields are set to retrieve
some system attribute. There is an example of how to call .TMIB at the end
of the TM_MIB(5) manual page. You would want to perform a GET operation
rather than the SET operation shown in that example.
Another option is to write a null service in one of your application servers
which just calls tpreturn() and have your client make periodic cals to that
service.
Calling a verb such as tpalloc() or tpconvert() would not be sufficient,
since these calls do not result in any network traffic.
2. The tperrordetail() function is available in newer releases of Tuxedo to
provide additional information about certain Tuxedo errors. When a
workstation client is disconnected, tperrordetail(0) will return TPED_TERM.
3. If there is a network failure, workstation clients must call tpinit() to
reauthenticate to the system. This is necessary for security reasons.
4. The keepalive option is passed down to the underlying network provider
and Tuxedo has no further involvement with keepalive once it informs the
network of this option. For Sockets the option passed is SO_KEEPALIVE; you
can do a web search on SO_KEEPALIVE to see exactly how the network treats
keepalive messages on your particular platform.
Ed
<Cacho Nakamura> wrote in message news:[email protected]...
Dear all,
I intend to automatically detect network failures from my workstation client
and have it attempt to reconnect to the server on its own.
Browsing the documentation for related information I saw the keep-alive
option. If I understood correctly you can have the workstation generate
periodic keep-alive messages to the server and if these are not
acknowledged, all subsequent ATMI calls will fail with TPESYSTEM.
My doubts regarding this are the following:
1) Is there some dummy ATMI function I can invoke periodically to check for
a disconnection? Otherwise network failures might go by unnoticed if there
are periods where my WSC doesn't require to communicate with the server.
2) Once I get a TPESYSTEM failure, is there some way to programatically
discriminate if the cause is a network disconnection? It is a pretty generic
error after all.
3) Once all ATMI functions start failing due to keep-alive detecting a
network failure, can the system recover on its own? or must I reconnect to
the server? What I mean is, maybe some keep alive messages where lost, the
system passes to the 'disconnected' state, but then the K.A. messages keep
being generated and upon correct acknowledgement of these, subsequent ATMI
calls will stop failing.
4) Does the WSC go to 'disconnected' state after the first unanswered keep
alive message? or is there some sort of tolerance like, say, 'If N messages
in a row are not answered then assume the connection to be dead'.
I'm sorry if it was too long a post, but neither searching the documentation
nor this forum clarified any of these issues for me.
Many thanks for your attention.
Regards.

Keep-alive message bridge connection

Hi,
I have setup messaging bridge between WLS 10.3.0.0 and a JBoss Messaging queque, after about 4 hours of inactivity in a queue bridge was disconneted, is there any way to configure keep-alive connection in WLS bridge ?
Thanks,
Lukasz

You can try to set the IdleTimeMaximum setting on your bridge configuration to a very large number. It specifies the maximum amount of time, in seconds, that a messaging bridge instance remains idle.
In “asynchronous” mode, this is the longest amount of time a messaging bridge instance stays idle before it checks the sanity of its connection to the source. In “synchronous” mode, this is the amount of time the messaging bridge can block on a receive call if no transaction is involved.
-Dongbo

3270 Emu program keep alive setup cause 7507(TN3270 Server) Down

Similar Messages

Maybe you are looking for