The following operators can be used to better focus your queries.
( ) , AND, OR, NOT, W/#
? single char wildcard, not at start
* multi char wildcard, not at start
(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.
Dynamically restart the Service Management Interface Tool (SMIT) during product firmware, microcode, or software installation to immediately enable new install features.
English (United States)
This text was extracted from a PDF file.
This is the abbreviated version, containing approximately
56% of the total text.
Page 1 of 1
DYNAMICALLY RESTARTING SMIT DURING PRODUCT CODE INSTALLATION
During firmware, microcode, or software installation, the existing Service Management Interface Tool
(SMIT) menus of the currently installed code level are used to direct and perform the new code
installation. When new install process related features are introduced by new code being installed, they
are effectively unavailable until the following code installation. This means that we are unable to take
immediate advantage of improvements.
The key idea of this article is to dynamically restart SMIT so that it uses the new menus and code support
associated with the new level being installed rather than deferring improvements to a subsequent
re-installation. The transition should be early in the install process, seamless, and not require specific
user action to initiate. Ideally, the user performing the new install would not even be able to detect the
transition to the control of the new code being installed. Unfortunately, there are security traps installed
that cause SMIT sessions to be logged out upon exit that must be worked around. One or more of the
following changes must be made:
Add special trap support to facilitate restarting SMIT with new menus at a specific interior menu. For
this case a specific signal (kill -N) or similar message would be sent to the SMIT process and the
updated trap handler would support the request.
Add a special bypass for the security trap that allows SMIT to be terminate...