HP Guardian Errors Manual page 257

Cause Another process called the CONTROLBUF procedure while referring to the receiver process
file.
Format The operating system sends the process the following message, provided the process has
opened its $RECEIVE file to receive file management system messages either by setting the
FILE_OPEN_ procedure parameter options.<15>to 0 or the OPEN procedure parameter flags.<1>to
1:
sysmsg[0] = -35
sysmsg[1] = operation parameter to the caller's
sysmsg[2] = count parameter to the caller's
CONTROLBUF
sysmsg[3] FOR n = buffer data from caller's CONTROLBUF,
Response Obtain the process ID of the caller to CONTROLBUF by a subsequent call to LASTRECEIVE
or RECEIVEINFO. The response, if any, is application dependent.
-37 PROCESS SETPARAM
Cause Another process referred to the receiving process in a SETPARAM call.
The operating system sends this message only if the receiving process has indicated it will accept
such messages by doing one of the following:
Omitting the FILE_OPEN_ procedure options parameter, or setting options.<15>= 0
Setting flags.<1>= 1 in its call to OPEN on $RECEIVE
Setting param1.<14>to 1 in a call to SETMODE 80
Format The layout of the received message described in terms of an array of words is:
sysmsg[1] = function parameter to SETPARAM
sysmsg[2] = Flags word:
.<14> = 1 if param-array was supplied in
the call to SETPARAM
.<15> = 1 if last-param-array was supplied
in the call to SETPARAM
sysmsg[3] = param-count parameter specified in the call
to SETPARAM
sysmsg[4:n] = param-array parameter to SETPARAM with a
length of param-count bytes
Response To return a value in the last-param-array parameter of the SETPARAM caller, the receiving
process should call REPLY with a buffer that has the following format:
replymsg[0] = -37
replymsg[1] = The value in the range 0 through 256 for
last-param-count
replymsg[2:n] = The value for last-param-array, with a
length of last-param-count bytes
If the format of the reply is incorrect, error code 2 is returned to both the caller of REPLY and the
caller of SETPARAM.
-38 QUEUED MESSAGE CANCELLATION
Cause A pending message was canceled. (A pending message is a message read by READUPDATE
but not yet replied to.)
This message can occur at random relative to other messages. For example, if an opener calls
CLOSE or FILE_CLOSE_ while it has an outstanding operation, the operational message is canceled
CONTROLBUF
where n is the number of words in
buffer
Message Descriptions 257