33 Please make changes to preamble and postscript wrappers as appropriate.
44 --->
55
6- # peer chaincode
6+ # cli chaincode
77
8- The ` peer chaincode` command allows users to invoke and query chaincode.
8+ The ` cli chaincode` command allows users to invoke and query chaincode.
99
1010## Syntax
1111
12- The ` peer chaincode` command has the following subcommands:
12+ The ` cli chaincode` command has the following subcommands:
1313
1414 * invoke
1515 * query
@@ -26,14 +26,14 @@ Args is an array of arguments of the function. For instance,
2626` {"Args":["GetAllAssets"]} ` is equivalent to
2727` {"Function":"GetAllAssets", "Args":[]} ` .
2828
29- Each peer chaincode subcommand is described together with its options in its own
29+ Each cli chaincode subcommand is described together with its options in its own
3030section in this topic.
3131
3232## Flags
3333
34- Each ` peer chaincode` subcommand has both a set of flags specific to an
34+ Each ` cli chaincode` subcommand has both a set of flags specific to an
3535individual subcommand, as well as a set of global flags that relate to all
36- ` peer chaincode` subcommands. Not all subcommands would use these flags.
36+ ` cli chaincode` subcommands. Not all subcommands would use these flags.
3737For instance, the ` query ` subcommand does not need the ` --orderer ` flag.
3838
3939The individual flags are described with the relevant subcommand. The global
@@ -75,12 +75,12 @@ values. For example, you will use `--peerAddresses localhost:9051
7575--peerAddresses localhost:7051` rather than ` --peerAddresses "localhost:9051
7676localhost:7051"`.
7777
78- ## peer chaincode invoke
78+ ## cli chaincode invoke
7979```
8080Invoke the specified chaincode. It will try to commit the endorsed transaction to the network.
8181
8282Usage:
83- peer chaincode invoke [flags]
83+ cli chaincode invoke [flags]
8484
8585Flags:
8686 -C, --channelID string The channel on which this command should be executed
@@ -108,12 +108,12 @@ Global Flags:
108108```
109109
110110
111- ## peer chaincode query
111+ ## cli chaincode query
112112```
113113Get endorsed result of chaincode function call and print it. It won't generate transaction.
114114
115115Usage:
116- peer chaincode query [flags]
116+ cli chaincode query [flags]
117117
118118Flags:
119119 -C, --channelID string The channel on which this command should be executed
@@ -141,17 +141,17 @@ Global Flags:
141141
142142## Example Usage
143143
144- ### peer chaincode invoke example
144+ ### cli chaincode invoke example
145145
146- Here is an example of the ` peer chaincode invoke` command:
146+ Here is an example of the ` cli chaincode invoke` command:
147147
148148 * Invoke the chaincode named ` mycc ` at version ` 1.0 ` on channel ` mychannel `
149149 on ` peer0.org1.example.com:7051 ` and ` peer0.org2.example.com:9051 ` (the
150150 peers defined by ` --peerAddresses ` ), requesting to move 10 units from
151151 variable ` a ` to variable ` b ` :
152152
153153 ```
154- peer chaincode invoke -o orderer.example.com:7050 -C mychannel -n mycc --peerAddresses peer0.org1.example.com:7051 --peerAddresses peer0.org2.example.com:9051 -c '{"Args":["invoke","a","b","10"]}'
154+ cli chaincode invoke -o orderer.example.com:7050 -C mychannel -n mycc --peerAddresses peer0.org1.example.com:7051 --peerAddresses peer0.org2.example.com:9051 -c '{"Args":["invoke","a","b","10"]}'
155155
156156 2018-02-22 16:34:27.069 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
157157 2018-02-22 16:34:27.069 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
@@ -176,28 +176,28 @@ Here is an example of the `peer chaincode invoke` command:
176176 successfully. The transaction will then be added to a block and, finally, validated
177177 or invalidated by each peer on the channel.
178178
179- Here is an example of how to format the `peer chaincode invoke` command when the chaincode package includes multiple smart contracts.
179+ Here is an example of how to format the `cli chaincode invoke` command when the chaincode package includes multiple smart contracts.
180180
181181 * If you are using the [contract-api](https://www.npmjs.com/package/fabric-contract-api), the name you pass to `super("MyContract")` can be used as a prefix.
182182
183183 ```
184- peer chaincode invoke -C $CHANNEL_NAME -n $CHAINCODE_NAME -c '{ "Args": ["MyContract:methodName", "{}"] }'
184+ cli chaincode invoke -C $CHANNEL_NAME -n $CHAINCODE_NAME -c '{ "Args": ["MyContract:methodName", "{}"] }'
185185
186- peer chaincode invoke -C $CHANNEL_NAME -n $CHAINCODE_NAME -c '{ "Args": ["MyOtherContract:methodName", "{}"] }'
186+ cli chaincode invoke -C $CHANNEL_NAME -n $CHAINCODE_NAME -c '{ "Args": ["MyOtherContract:methodName", "{}"] }'
187187
188188 ```
189189
190- ### peer chaincode query example
190+ ### cli chaincode query example
191191
192- Here is an example of the `peer chaincode query` command, which queries the
192+ Here is an example of the `cli chaincode query` command, which queries the
193193peer ledger for the chaincode named `mycc` at version `1.0` for the value of
194194variable `a`:
195195
196196 * You can see from the output that variable `a` had a value of 90 at the time of
197197 the query.
198198
199199 ```
200- peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'
200+ cli chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'
201201
202202 2018-02-22 16:34:30.816 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
203203 2018-02-22 16:34:30.816 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
0 commit comments