JOB_DESTINATION_ID{
destination_id=ID-name
}

• destination_id=ID-name
  Specify an existing ID name. You can also specify relays managing the ID to limit the relay systems that execute the ID group job. If you specify relays managing the ID, begin each specified relay with a backslash (\). The ID name itself begins with a backslash (\) and a percent sign (%).
  If you do not specify a relay managing the ID, execution is performed on all relays managing the ID to which that ID group is registered.
  The following is an example of an ID name specification:
  

  destination_id=\dmp202\%ID0001

  Specify the names of the relays managing the ID according to the working key of each of the relays managing the ID that is specified. For example, if the working key of the higher-level relay managing the ID is its host name, and the working key of the lower-level relay managing the ID is its IP address, specify the destination as follows: \host-name\IP-address\%ID-name.
  To specify multiple ID groups, use the semi-colon (;) to delimit the ID names. You can also code destination_id= on multiple lines to specify multiple ID groups. A total of 200 ID groups can be specified.
  

• The JOB_DESTINATION and JOB_DESTINATION_ID tags are mutually exclusive. In command-argument specifications, /h, /g, /dc, /dg, and /do cannot be specified together with /X.
• You cannot specify a relay managing the ID if you are using a parameter file with the dcmcoll command or the dcmsusp command. If you do specify one, an error results when the command executes.
• If you specify a relay managing the ID, the length of the destination string must not exceed 256 bytes, including the ID name.
• If you execute the command with specification of a relay system that does not exist, the job is created but will not execute.