The rsrc.cib operates on a batch file that includes a line for each component that will be checked in. Batch files enable you to check-in large numbers of component with a single command.
Each line in the batch file corresponds to a single component on the local machine that will be checked in as a single component. Each line consists of a series of fields that are separated by the pipe character (|). Some fields are optional and may be omitted. If an optional field is omitted but is followed by other fields, the omitted field should be followed by a | character, so that rsrc.cib can accurately identify each field.
You can include comments in a batch file. Any line that begins with the pound character (#) is interpreted as a comment.
The following table describes the syntax of a line of a batch file.
Table 3–39 Syntax of a Line in a Batch File
Content |
Optional/Required |
---|---|
The location of the component on the local machine |
Required |
The name to be assigned to the component when checked in |
Required |
The component type |
Required |
The platform the component is intended for expressed as a HostSetID in the form NM:<platform_name>, where <platform_name> is one of the platform names listed in Table 3–40. |
Optional |
A description of the component |
Optional |
A boolean designation of whether the file is a configuration file |
Optional (Default is false) |
A boolean designation of whether check-in should be assigned a major version number (e.g., 2.0) |
Optional (Default is false) |
A boolean designation of whether to hide the previous most recent version of the component |
Optional (Default is true) |
A boolean designation of whether to include owner information when storing permissions information |
Optional (Default is true) |
A boolean designation of whether to include group information when storing permissions information |
Optional (Default is true) |
A boolean designation of whether the files being checked in should be added to the existing files to create a new version, instead of creating a new version by completely replacing the existing files |
Optional (Default is true) |
If this component is being checked in a from a host, the host ID of the host from which the component is being checked in |
Optional |
A boolean designation of whether redundancy checking should apply |
Optional (Default is true) |
The name of the picker to use (optional, defaults to null for the default picker) | |
A Hashtable in string form containing extra options supported by the type's exporter. Note that the boolean values for the following cannot be specified using the extraOpts argument:
Instead, use the batch file format equivalent options to specify these values. |
The following table lists the names that you can use in the fourth field of a batch file line to specify a platform for the component.
Table 3–40 Names for Platforms
Platform Name |
Description |
---|---|
any |
Any platform supported by the Sun N1 Service Provisioning System software |
AIX - any version |
Either IBM AIX 5.1 or IBM AIX 5.2 |
AIX 5.1 |
IBM AIX 5.1 |
AIX 5.2 |
IBM AIX 5.2 |
Solaris - any version |
SolarisTM 6, Solaris 7, or Solaris 8 releases |
Solaris 7 |
Solaris 7 release |
Solaris 8 |
Solaris 8 release |
Solaris 9 |
Solaris 9 release |
Solaris 10 |
Solaris 10 release |
Windows 2000 Server |
Microsoft Windows 2000 Server |
Red Hat Linux |
Red Hat Advanced Server 2.1 |