(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*

This guide provides a more detailed description of the syntax that is supported along with examples.

This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.

Concept Search - What can I type?

For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.

Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.

The method
consists of three steps. The first step
is to bind
to the core Daemons remotely. The second
step is to send the Audit
Event Records to the main Audit Trail.
The last step is to list all
possible actions that DCE Users could take after the Daemon was
killed abnormally.

To achieve
the first step, it is necessary to create two files
during configuration time for each Monitored Daemon. The first file
is called daemon_identity, and it contains the Host name where the
Daemon is going to reside. The second
file is called daemon_binding
and it contains the String Bindings of the Daemon. The examples of
these two files are shown below:
o The daemon_identity file:
hosts/dceos2.austin.ibm.com/self
o The daemon_binding file:
ncacn_ip_tcp:129.35.69.22(1117)
ncacn_ip_udp:129.35.69.22(1122)

These two
files will be placed in /opt/dcelocal/var/<component>
sub-directory of the machine where the Monitoring Tool periodically
runs. The Monitoring Tool should run on
the same system with DCED.
For example:

(Image Omitted)

The purposes of creating these two files are:
1.
To allow the Monitoring Tool to bind to the Monitored
Daemons remotely for auditing.
2.
To permit the Monitored Daemons to send the Audit Records
to the main central Audit Trail
file, which is controlled
by Audit Daemon, before they were
killed.

Recall, the
Monitoring Tool is an Application Program which
periodically listens to the Monitored Daemons via a RPC call. It can
be easily implemented by the means of SMP and EMS. In the scope of
this paper, it will not be discussed in detail (Refer to SMP and EMS
functions for more details on how to implement the Monitoring Tool).