Browse Prior Art Database

Introducing Wrapper commands, Their Access methods, and the Wrapper Command Utility

IP.com Disclosure Number: IPCOM000236019D
Publication Date: 2014-Apr-02
Document File: 3 page(s) / 25K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method of utilizing wrapper commands and wrapper command utility to provide a system administrator the ability to quickly configure a machine to have the best first data capture preparation for important commands on the system is disclosed. The disclosed method provides the capability to have First Data Capture tracing when a defect occurs.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 40% of the total text.

Page 01 of 3

Introducing Wrapper commands, Their Access methods, and the Wrapper Command Utility

Disclosed is a method of utilizing wrapper commands and wrapper command utility to provide a system administrator the ability to quickly configure a machine to have the best first data capture preparation for important commands on the system. The disclosed method provides the capability to have First Data Capture tracing when a defect occurs.

Some sample problems that often occur in attempting to have sufficient First Data Capture are:

After analyzing data sent in, Software Support calls customer stating that there was


1.

not enough data to solve the problem because a system trace was not running when the problem occurred.

After analyzing data sent in, customer gets a call back from Software Support that


2.

although a trace was running when problem occurred, there is still not enough data because the level of trace verbosity (amount of data) was too low when the problem occurred
After analyzing data sent in, customer gets a call back from Software Support that


3.

there was not enough data to solve problem because the log of trace data wrapped when the problem occurred. This can happen when the customer gets an error message when the problem occurs. The error message may suggest some actions to take to fix problem. In taking these actions (usually other commands) the log data of the original problem that was captured may be written over by other log data that was written to the log by these other commands. This is called log wrap.

After analyzing data sent in, customer gets a call back from Software Support stating


4.

it would help to solve the problem if the customer could give a history of filesystem commands run and a time line of when they occurred. Often there is more then one system administrator and there is no central history or time line kept by anyone so that information is not available.

All of the above problems may be solved by utilizing wrapper commands which are administered by the Wrapper Command Utility.

In addition, another problem may arise after having receiving First Data Capture data. Subsequently, there may be a need to send some kind of debug object such as a debug kernel, debug command, or debug kernel extension to the customer. Usually there are instructions that need to be sent on how to start traces, increase the system settings for more debug data output, and make sure all logs are set up to receive output. It can be a challenge for some system administrators to get everything set up correctly and also brought back to a default state after the debug testing is over.

All the above problems can be dealt with easier with providing the Wrapper Command Utility with the debug object.

1


Page 02 of 3

A "Wrapper Command" is a script with the same name as a well-known command such as chfs that exists in a central location. The wrapper script calls the same command that it is named after, but it also contains pre-processing command...