# irda.pod: IRDA Manual Pages # $Id: irda.pod,v 1.6 2015/05/08 18:10:18 RDA Exp $ # ARCS: $Header: /home/cvs/cvs/RDA_8/src/scripting/lib/Pod/en/irda.pod,v 1.6 2015/05/08 18:10:18 RDA Exp $ =for stopwords irda =head1 NAME irda - Remote Diagnostic Agent Interface for Incident Packaging System =head1 SYNOPSIS irda.pl [-ioqsv] [-t lvl] [-e list] request irda.pl -C [-fv] [-t lvl] irda.pl -I [-fv] [-t lvl] [-c proto] dir ... See the following sections for additional information about the switches. =head1 DESCRIPTION The Incident Package System (IPS) can trigger a Remote Diagnostic Agent (RDA) collection when finalizing an incident package. IPS expects to find the RDA start scripts in the F subdirectory of the Oracle home. However, you can put the RDA software somewhere else, for example, on a shared drive. In that case, the subdirectory contains the start scripts and its configuration file only. RDA derives the collection requirements from request file parameters by using rules. It suppresses all interactive dialogues in setup and all user acknowledge requests in the data collection or tests. For more information about RDA, or to download the latest version, see My Oracle Support documents 314422.1 and 330363.1. =head2 INTERFACE SCRIPT irda.pl [-ioqsv] [-t lvl] [-e list] request Executes an IPS request. IPS provides the full path of the request file as an argument. =head2 RULE CHECK irda.pl -C [-fv] [-t lvl] Checks the consistency of the rule files. You can use the B<-f> option to extend the validation rules. =head2 BOOTSTRAP INSTALLATION irda.pl -I [-fv] [-t lvl] [-c proto] dir ... Installs the RDA bootstrap in the specified Oracle home directories. It copies the interface script and creates a configuration file F in an F subdirectory. It aborts the installation when the subdirectory exists already. You can force the installation with the B<-f> option. You can use the B<-c> option to indicate a prototype for generating the configuration file. RDA keeps the extension of the prototype for the configuration file. F can coexist with operating system-specific variants: C, C, and C. RDA gives preference to the variants corresponding to the current platform. =head1 COMMON OPTIONS =over 8 =item B<-e key=value[,...]> Specifies a temporary value for one or more settings. RDA converts the setting names automatically to upper case and separates the different assignments by commas. =item B<-f> Sets full/force mode for the B<-C> and B<-I> options. =item B<-i> Reads settings from the standard input. =item B<-o> Disables standard output and error redirections. =item B<-q> Sets the quiet mode. =item B<-s> Saves the collector definition. =item B<-t lvl> Enables tracing of the setup and data collection commands globally. =item B<-v> Sets the verbose mode. =back =head1 CONFIGURATION FILES The configuration files control the relocation mechanism but you can also use them for controlling the RDA operations. The configuration files can contain following parameters: =over 17 =item B Specifies a temporary value for one or more settings as for the B<-e> option. =item B Full path to an alternative filter definition. =item B Full path to the RDA software directory. =item B Sets the trace level. =item B Disables the progress reporting. =item B Indicates which trace level RDA must activate for the prepare phase. You can specify 0 or 1 as the trace level. =item B Name of the command to execute, F by default. =item B Sets the verbose mode. =item BnameE> Specifies a value for a preparation setting. For example, C =item BmoduleE> Indicates which trace level RDA must activate for the corresponding module. You can specify 0, 1, or 2 as the trace level. For example, C =back =head1 COPYRIGHT NOTICE Copyright (c) 2002, 2016, Oracle and/or its affiliates. All rights reserved. =head1 TRADEMARK NOTICE Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. =cut