- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: File Transfer
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО12-29-2010 09:52 AM
тАО12-29-2010 09:52 AM
File Transfer
Stand alone interactive ftp will move 5 megs in .05 seconds (one twentieth of a second)between the two systems. If I put that same ftp into a subprocess that uses a system service call to sys$creprc to execute the ftp is takes nearly 90 seconds. I suspect a buffer/socket size issue somewhere.
I know the sys$creprc system service call uses the sysgen PQL params for quotas - and I have the PQL values set to the same values as the authorize values used by the interactive user.
What am I missing? Any ideas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 12:06 PM
тАО12-29-2010 12:06 PM
Re: File Transfer
Thomas Pfau (pfau) wrote a callable ftp a while back as another potential approach available here, and that source code has been posted at various sites.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 01:10 PM
тАО12-29-2010 01:10 PM
Re: File Transfer
As an experiment, what happens if you replace your $CREPRC with a LIB$SPAWN equivalent?
Also be VERY VERY careful about your PQL structure. It's unaligned and can be tricky to convince a compiler to layout correctly. To make absolutely certain it's correct, run your code under DEBUG and STEP/INTO the system service, then EXAMINE/HEX the PQL structure, making sure you can correctly decode the byte/long byte/long records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 01:14 PM
тАО12-29-2010 01:14 PM
Re: File Transfer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 01:24 PM
тАО12-29-2010 01:24 PM
Re: File Transfer
Appreciate the help. Reps coming.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 07:06 PM
тАО12-29-2010 07:06 PM
Re: File Transfer
>running as a shareable subroutine out of a
>shareable library, I didn't have the
>standard CLI easily available.
Not sure I understand this. Unless you're running as a "naked" detached process you have a CLI and should be able to call LIB$SPAWN.
Whatever, to diagnose the issue, I'd suggest you extract the FTP operation and execute it independently of whatever else code you have. Your SPAWN test could be a one liner:
status=LIB$SPAWN('@DO_FTP')
Try other ways of executing the same effective command, SUBMIT, SPAWN, interactive, etc... 0.05secs to 90 seconds is a rather serious difference. Not one I'd expect to see from mere tuning.
Relying on default and/or minimum PQL SYSGEN parameters for a $CREPRC is a recipe for a headaches in the future. You WILL forget that you're dependent on them, and when you move the code or upgrade you'll have to diagnose why it mysteriously fails. To save your sanity, make sure all process creations (RUN/DETACHED or $CREPRC) have fully populated PQLs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 08:25 PM
тАО12-29-2010 08:25 PM
Re: File Transfer
I agree that relying on the PQL quotas can be problematic. All the quotas are now explicitly defined in my call to sys$creprc!
Thanks for all the suggestions.