 |
» |
|
|
|
Allows a created process to retrieve information strings passed
to it by its creator in the RPMCREATE
call. Syntax | |
RPMGETSTRING (rpmstring,rpmstringlen,result) |
Parameters | |
- rpmstring
(output)
Character array, by reference.
The string passed in the opt parameter
of the RPMCREATE call that created
this process. - rpmstringlen (input/output)
32-bit integer, by reference.
The maximum byte length allowed for the rpmstring. The returned
value indicates the actual length of the returned rpmstring, zero
if no string was passed by the creator process. - result (output)
32-bit integer, by reference. The
error code returned; zero if no error.
Description | |
The RPMGETSTRING intrinsic
allows a process created by an RPMCREATE
to obtain the information string passed to it by the creator process
in the RPMCREATE call. All the
parameters are required.The string obtained in this manner may contain
any useful information. For example, it could contain the name of
a (call) socket belonging to the creator along with the name of
the node on which the creator is executing. The created process
can look up this socket name in order to acquire a destination descriptor
for it. After creating a socket of its own, it can establish a connection
to the creator process. If the opt parameter of RPMCREATE
contained more than one RPM string, you can issue several RPMGETSTRING
calls to retrieve the strings. For example: Creator process: ADDOPT (Opt, 0, 20000, Length1, RpmString1); ADDOPT (Opt, 1, 20000, Length2, RpmString2); ADDOPT (Opt, 2, 20000, Length3, RpmString3); RPMCREATE (... Opt ...); |
Created process: RPMGETSTRING (RpmString1, Length1, Result); RPMGETSTRING (RpmString2, Length2, Result); RPMGETSTRING (RpmString3, Length3, Result); |
For another illustration of the use of this intrinsic, see
the program examples at the end of this chapter. |
