Hi, Cheng
>>> I noticed some commands take target operand, and others take target
>>> options. What's the rules for providing target value?
>>>
>>> For ex:
>>>
>>> asadmin list-components --target cluster1 (Failed as option)
>>> Invalid option: --target
>>>
>>> asadmin list-components cluster1 (Passed as operand)
>>> Command list-components executed successfully on server instance
>>> instance1
>>> Command list-components executed successfully on server instance
>>> instance2
>> Yes, I have implemented the list-components command to be v2 backward
>> compatible (though like Bill I am not sure why it was operand instead
>> of an option).
>>> (The doc says for list-components, the target operand is deprecated
>>> and ignored. But it turns out it's still significant)
>> Where do you see this? We should change this to say the same thing as
>> v2 doc as we are implementing the same way.
>>
>
> V3 reference manual:
> http://docs.sun.com/app/docs/doc/820-7701/list-components-1?l=en&a=view
>
> and asadmin help page in 3.1 and 3.0.1:
>
> GF3.0.1/bin > asadmin list-components --help displays:
> ... ...
> OPERANDS
> target
>
> Do not specify this option. This option is retained for
> compatibility with other releases. If you specify this
> option, a syntax error does not occur. Instead, the
>
> Java EE 6 Last change: 14 Sep 2009 1
>
> subcommand runs successfully and the option is silently
> ignored.
>
I see. I think this meant to say that the target option is not yet
supported in the v3 release (as the only possible target for v3 is DAS).
The 3.1 doc should say the same thing as v2.1 about the target option.
Thanks,
- Hong