- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- BASIC script access to /dev/stdin,stdout,stderr
Operating System - HP-UX
1756735
Members
2876
Online
108852
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
Discussions
Discussions
Forums
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
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
тАО05-21-2002 06:52 AM
тАО05-21-2002 06:52 AM
BASIC script access to /dev/stdin,stdout,stderr
We have a third-party application
developed on a different platform. It
is transportable to many platforms, but
in the case of HP, it has an issue. It
is written in BASIC and requires
(normal functionality) access to stdin,
stdout, and stderr, which it cannot
access directly internally by device
number. This is accomplished by
referencing /dev/stdin, etc on other
systems but HP doesn't have these files.
How can this be accomplished on HP?
developed on a different platform. It
is transportable to many platforms, but
in the case of HP, it has an issue. It
is written in BASIC and requires
(normal functionality) access to stdin,
stdout, and stderr, which it cannot
access directly internally by device
number. This is accomplished by
referencing /dev/stdin, etc on other
systems but HP doesn't have these files.
How can this be accomplished on HP?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2002 07:05 AM
тАО05-21-2002 07:05 AM
Re: BASIC script access to /dev/stdin,stdout,stderr
Have you tried creating named pipes for /dev/stdin, etc.? Also, could you post how you would initiate running the BASIC program?
mark
mark
the future will be a lot like now, only later
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2002 07:14 AM
тАО05-21-2002 07:14 AM
Re: BASIC script access to /dev/stdin,stdout,stderr
Try to link /dev/tty
to /dev/stdin /dev/stdout /dev/stderr
ln /dev/tty /dev/stdin
See on others systems is that files are linked to anyother specila files and check if major and minor for /dev/stdin are equal to anyothers in /dev.
Just thinks.
unsupported
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2002 07:51 AM
тАО05-29-2002 07:51 AM
Re: BASIC script access to /dev/stdin,stdout,stderr
Thank you for your very prompt replies! I apologize for the delay in response, I've been out of town AND have not received a test program from the vendor to test your solutions (They are rather over-protective of thier software). This uses Thoroughbred basic and would be normally be executed via a statement similar to "./b IPLNAME", where the IPLNAME is the 'template' that assigns the devices. They have moved the task to a (Caldera) server that does not have this issue to resolve. I would still love to test this to see why they couldn't get it to work!
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP