HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ftam : ftam_init hangs after IP communications cut
Operating System - HP-UX
1832650
Members
2767
Online
110043
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2001 01:20 AM
07-16-2001 01:20 AM
Ftam : ftam_init hangs after IP communications cut
Hi
We use FTAM to transfert files between systems
(on IP). We use
* On HPUX 10.20 : FTAMS800 E.04.00 + PHNE_16637
* On HPUX 11.00 : J2163 E.06.00 + PHNE_19502
Or problem is : when we transfert a file and cut
IP communication (unplug network link for example)
ftam_init never stop (we test more than 23 hours).
When we plug network link ftam_init doesn't stop.
Our applications wait for a reply and all are
hangs...
Do you know this problem ? Do you know a patch
or a configuration parameter to correct it ?
Thanks by advance
Herv?
We use FTAM to transfert files between systems
(on IP). We use
* On HPUX 10.20 : FTAMS800 E.04.00 + PHNE_16637
* On HPUX 11.00 : J2163 E.06.00 + PHNE_19502
Or problem is : when we transfert a file and cut
IP communication (unplug network link for example)
ftam_init never stop (we test more than 23 hours).
When we plug network link ftam_init doesn't stop.
Our applications wait for a reply and all are
hangs...
Do you know this problem ? Do you know a patch
or a configuration parameter to correct it ?
Thanks by advance
Herv?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2001 06:06 AM
07-16-2001 06:06 AM
Re: Ftam : ftam_init hangs after IP communications cut
Well on your 10.20 system you behind in the patch. That patch was superceded by PHNE_17861 or PHNE_17525. Several SR show that the defects fixed on that patch PHNE_16637was that the Abort:
4. SR 1653261453:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
5. SR 1653261461:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
6. SR 1653261487:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
7. SR 1653261479:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
8. SR 5003439562:
Invalid prototypes for FTAM API functions in mapftam.h
was causing compilation errors with ANSIC compilers.
You may want to check and see if you have the same situation for your 11.0 box. It may be a simple matter of putting in the best or latest patch.
Hope this helps,
Rita
4. SR 1653261453:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
5. SR 1653261461:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
6. SR 1653261487:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
7. SR 1653261479:
FTAM Protocol Abort was not being sent when the
F-INITIALIZE response contained invalid mandatory
parameters.
8. SR 5003439562:
Invalid prototypes for FTAM API functions in mapftam.h
was causing compilation errors with ANSIC compilers.
You may want to check and see if you have the same situation for your 11.0 box. It may be a simple matter of putting in the best or latest patch.
Hope this helps,
Rita
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP