- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: C++ and SYS$QIO
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
тАО10-07-2003 07:33 PM
тАО10-07-2003 07:33 PM
Why do I keep getting %SYSTEM-F-BADPARAM, bad parameter value ????????
Here's a niipet of the QIO I am issuing in a C++ object:
/*
** Active open connection by client:
** Setup extended characteristics buffer
** Issue $QIO to open connection
** IO$SETMODE | IO$M_CTRL | IO$M_STARTUP
*/
ecb[0].paraID = 2; /* internet address */
ecb[0].val = htonl( inet_network (serverIPAddress) );
ecb[1].paraID = 3; /* port number */
ecb[1].val = port;
ecb_dsc.dsc$w_length = sizeof(ecb);
ecb_dsc.dsc$b_dtype = DSC$K_DTYPE_T;
ecb_dsc.dsc$b_class = DSC$K_CLASS_S;
ecb_dsc.dsc$a_pointer = (char *)&ecb;
memset ( &connect_iosb, 0, sizeof(IOSB_T) );
status = sys$qio( 0,
ChannelNo,
val,
&connect_iosb,
&processConnectAST, 0,
0,
&ecb_dsc,
0,0,0,0);
It all compiles OK but when the AST fires and I check the connect_iosb status value - it is 20 which means Bad Param Value ???
Please can anyone help ??
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2003 09:31 PM
тАО10-07-2003 09:31 PM
Re: C++ and SYS$QIO
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2003 02:23 AM
тАО10-08-2003 02:23 AM
Re: C++ and SYS$QIO
Yeah, make sure that this ecb and stuff it points to is not local to the routine setting up for the ast, but availble when the as executes? make static and see if that helps?
What Driver is this? I check the VMS TCP programmign manual (http://h71000.www7.hp.com/doc/73final/6529/6529pro_index.html) and find no reference about IO_CTRL | M_STARTUP nor 'ecb's.
Specifically I wanted to verify you really needed a descriptor, and not an itemlist.
Descriptors in QIOs are not too common, and and ecb does not look like a 'fixed length character string' to me.
fwiw,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2003 09:38 PM
тАО10-09-2003 09:38 PM
Re: C++ and SYS$QIO
If I understand what you will make, processConnectAST is a your function; if is it you could write:
status = sys$qio( 0, // param #1: efn
ChannelNo, // param #2: I/O channel
val, // param #3: function code
&connect_iosb, // param #4: I/O status block
0, // param #5: AST mask, here may be a value
0, // param #6: no param supplyed
&processConnectAST, // p. #7: your fun addr
&ecb_dsc, // p. #8: param 4 your function
0,0,0,0);
Notice compiler don't warning you because size of parameters are coherents.
Bye
Antoniov
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2003 09:45 PM
тАО10-09-2003 09:45 PM
Re: C++ and SYS$QIO
Bye
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2003 10:58 PM
тАО10-09-2003 10:58 PM
SolutionYou'll find there that:
- the IO fucntion will be unknown.
- the parameter set that you use is not correct for IO$_SETMODE.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2003 11:08 AM
тАО10-10-2003 11:08 AM
Re: C++ and SYS$QIO
http://h18000.www1.hp.com/support/asktima/communications/00A1302D-E940C6C9-1C02A1.html
If your intention is to write $QIO based TCP/IP communications, please have a look at:
http://h18000.www1.hp.com/support/asktima/communications/009E9CF1-C62D69C0-1C0186.html
If none of these needs apply to yours, please reply telling us what you intend to do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2003 07:41 PM
тАО10-13-2003 07:41 PM
Re: C++ and SYS$QIO
I found some of the links very useful so once again a big thank-you