Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to access windows pipes in cobol
- Thread starter tonyc1
- Start date
- Thread starter
- #3
Thank you for replying. I've made some progress. It seems that when trying to call "CallNamedPipe" (from Kernel32.lib) I didn't have the right amount of parameters and it would not let me link the program. Now if anyone knows what I should be putting in for the parameters of "CallNamedPipe" that might help me get further!
thanks
Tony
thanks
Tony
Hello Tony
Take care using Api calls.
There are few things you have to know before use any Api calls.
First of all, search on the "Kernel32.lib" file with a normal text editor like Notepad, for the word (function) you want to use: "CallNamedPipe".
Normally, an Api call can be made in Ascii mode.
Seeing the result editing, we found that the "CallNamedPipe" has an "A" suffix at end of its name.
This could means the call must be done in Ascii mode like:
CALL "CallNamedPipeA" WITH STDCALL LINKAGE
USING by value parm1
by value parm2
by value parm2
Of course, the "Kernel.lib" file must be included on the project as an external resource.
Each of these "parm" fields must be defined PIC S9(9) COMP-5.
The value "28" you will find searching on the "Kernel32.lib", means that the call need 3 parameters passed from the caller and each parm must be declared as a long field (S9(9) COMP-5).
An advice: you can download a good api reference from This guide offers a variety of the best and used api calls as in Vb and, of course, you can use them also with Fujitsu cobol or Powercobol.
Let me know if this hints help you.
Regards
Gianni
Take care using Api calls.
There are few things you have to know before use any Api calls.
First of all, search on the "Kernel32.lib" file with a normal text editor like Notepad, for the word (function) you want to use: "CallNamedPipe".
Normally, an Api call can be made in Ascii mode.
Seeing the result editing, we found that the "CallNamedPipe" has an "A" suffix at end of its name.
This could means the call must be done in Ascii mode like:
CALL "CallNamedPipeA" WITH STDCALL LINKAGE
USING by value parm1
by value parm2
by value parm2
Of course, the "Kernel.lib" file must be included on the project as an external resource.
Each of these "parm" fields must be defined PIC S9(9) COMP-5.
The value "28" you will find searching on the "Kernel32.lib", means that the call need 3 parameters passed from the caller and each parm must be declared as a long field (S9(9) COMP-5).
An advice: you can download a good api reference from This guide offers a variety of the best and used api calls as in Vb and, of course, you can use them also with Fujitsu cobol or Powercobol.
Let me know if this hints help you.
Regards
Gianni
Hello again, Tony
Take a look over this link:
You will find a good explanation on the parameters you have to declare to use the "CallNamedPipe" APi call.
Gianni
Take a look over this link:
You will find a good explanation on the parameters you have to declare to use the "CallNamedPipe" APi call.
Gianni
This is the complete Vb declaration:
Declare Function CallNamedPipe Lib "kernel32" Alias "CallNamedPipeA" (ByVal lpNamedPipeName As String, lpInBuffer As Any, ByVal nInBufferSize As Long, lpOutBuffer As Any, ByVal nOutBufferSize As Long, lpBytesRead As Long, ByVal nTimeOut As Long) As Long
Note that the "string" must be declared on cobol BY REFERENCE and each "long" field must be PIC S9(9) COMP-5.
About the type "Any", you can use string or numeric fields.
Gianni
Declare Function CallNamedPipe Lib "kernel32" Alias "CallNamedPipeA" (ByVal lpNamedPipeName As String, lpInBuffer As Any, ByVal nInBufferSize As Long, lpOutBuffer As Any, ByVal nOutBufferSize As Long, lpBytesRead As Long, ByVal nTimeOut As Long) As Long
Note that the "string" must be declared on cobol BY REFERENCE and each "long" field must be PIC S9(9) COMP-5.
About the type "Any", you can use string or numeric fields.
Gianni
more....
Take a look at:
This web site contains more important pages about the Windows API. It's a good api reference.
Gianni
Take a look at:
This web site contains more important pages about the Windows API. It's a good api reference.
Gianni
- Thread starter
- #8
- Status
Similar threads
