ins_create

ins_create [-d destsys] -a appname -r restyp [-I {AUTORES_ISP|INIT_ISP|INIT_OSU}][-v info] -t tag -i id [-Q quickChkInt][-D deepChkInt][-l localRecover{Y|N}] [-s AUTOMATIC|INTELLIGENT]

Defines a new resource instance on system destsys in the configuration database. The resource instance is described by the arguments given. If destsys is not specified, the current system is assumed. The command offers the following string tag options:

• The -a and -r options indicate the preexisting application and resource type associated with this new instance.

• Initialization type field specified by the -I option indicates how the resource instance should be initialized if LifeKeeper restarts (for example, at boot time).

• Optional string info specified by the -v option is a field that can contain additional resource type specific information and does not necessarily have to be unique per resource type.

• String tag specified by the -t option is a string that names the resource instance and is unique on a system. It is a string that is meaningful externally to LifeKeeper. String tag specified by the -t option is a string that names the resource instance and is unique on a system. It is a string that is meaningful externally to LifeKeeper. Note: The tag name must consist of printable ASCII characters.

• String id specified by the -i option is also unique per system, but may be meaningful only internally to LifeKeeper.

• Quick check interval provided with -Q option should be in seconds. The value should be zero if quickchk.ksh script doesn’t exist for the resource. LifeKeeper waits this interval time between two consecutive execution of quickchk.ksh script. Valid range of value: 0 – 604800.

• Deep check interval provided with -D option should be in seconds. The value should be zero if deepchk.ksh script doesn’t exist for the resource. LifeKeeper wait this interval time between two consecutive execution of deepchk.ksh script. Valid range of value: 0 – 604800.

• Local recover option indicates whether resource should be recovered by executing recover.ksh script. This option should be “N” if recover.ksh script doesn’t exist for the resource.