[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]

Files Reference

Resource Data Input File


Input file for passing both resource class and resource attribute names and values to the Resource Monitoring and Control command-line interface (CLI). The data in this file is used for defining resources or for changing persistent attribute values of a resource or resource class.


The Resource Data Input File is used in conjunction with the -f command line flag to pass resource persistent attribute values to the RMC CLI in cases where using the command line directly would be too cumbersome or too prone to typographical errors. This file has no set location. It can be a temporary or permanent file, depending on requirements.

The mkrsrc and chrsrc commands read this file when they are issued with the -f flag. The lsrsrcdef and lsactdef commands generate a file with this format when issued with the -i flag.

Persistent attribute names and values for one or more resources for a specific resource class used to define a new resource or change attribute values for an existing resource. The persistent resource attributes are read in by the commands mkrsrc and chrsrc. These attributes are ignored if the input file is read by the chrsrc command that has been specified with the -c flag.

Persistent attribute names and values for a resource class used to change the attribute values of an existing resource class. The persistent resource class attributes are read in by the command chrsrc only when the -c flag is specified.

In general, the Resource Data Input File is a flat text file with a format as follows (bold words are literal). Note that text preceding any single colon is an arbitrary label and may be any alphanumeric text.

# This is a comment
      AttrName1  = value 
      AttrName2  = value 
      AttrName3  = value 
    another label:
        Name        = name
        NodeNumber  = 1
      SomeSettableAttrName 					= value
      SomeOtherSettableAttrName 			= value

See the Examples section for more details.

Format points:


  1. Example of input file for IBM.Foo resource used by the following sample mkrsrc command. Comments are arbitrary:
    mkrsrc -f /tmp/my_resource_data_input_file IBM.Foo

    The file consists of:

    # Resource 1 - only set required attributes 
    resource 1:
        NodeList = {1}
    # Resource 2 - setting both required and optional attributes
    # mkrsrc -e2 IBM.Foo displays required and optional
    # persistent attributes 
    resource 2:
        NodeList = {1}
        Int32 = -99
        Uint32 = 99
        Int64 = -123456789123456789
        Uint64 = 123456789123456789
        Float32 = -9.89
        Float64 = 123456789.123456789
        String = "testing 123"
        Binary = 0xaabbccddeeff
        RH = "0x0000 0x0000 0x00000000 0x00000000 0x00000000 0x00000000"
        SD = [hello,1,{2,4,6,8}]
        Int32Array = {-4, -3, -2, -1, 0, 1, 2, 3, 4}
        Int64Array = {-4,-3,-2,-1,0,1,2,3,4}
        Uint32Array = {0,1,2,3,4,5,6}
        Uint64Array = {0,1,2,3,4,5,6}
        Float32Array = {-3.3, -2.2, -1.2, 0, 1, 2.2, 3.3}
        Float64Array = {-3.3, -2.2, -1.2, 0, 1, 2.2, 3.3}
        StringArray = {abc,"do re mi", 123}
        BinaryArray = {"0x01", "0x02", "0x0304"}
        RHArray     = {"0x0000 0x0000 0x00000000 0x00000000 0x00000000 0x00000000",
     "0xaaaa 0xaaaa 0xbbbbbbbb 0xcccccccc 0xdddddddd 0xeeeeeeee"}
        SDArray     = {[hello,1,{0,1,2,3}],[hello2,2,{2,4,6,8}]}
  2. Example of an input file for changing the attribute values of existing IBM.Foo resources.
    chrsrc -f  /tmp/Foo/ch_resources -s 'Name == "c175n05"' IBM.Foo

    The file consists of:

    # Changing resources that match the selection string entered
    # when running chrsrc command.
    	resource 1:
            String            = "this is a string test" 
            Int32Array        = {10,-20,30,-40,50,-60} 

Related Information

The chrsrc command , lsactdef command, lsrsrcdef command, and mkrsrc command.

The rmccli General Information file.

[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]