This command re-executes the job startup program in a parameter file under the managing server.

dcmrtry.exe [retry-key]
             /i parameter-file-name /o result-output-file-name
            [/LC {ON|OFF}]

• retry-key
  Specify the job status of the job to be executed. Specify a key after the command name. You can specify ERROR, WAIT or PENDING in any combination. When specifying keys in combination, separate the keys with spaces. The default is ERROR.
  
  • ERROR
    Re-executes the job that ended in error.
    
  • WAIT
    Re-executes the job that is waiting for execution.
    
  • PENDING
    Re-executes the job in which a temporary communication error occurred.
    
• /i
  Specify the full path for the parameter file to be used.
  You can also use the output file from the dcminst command (without the /s specification), the dcmcoll command (without the /s specification), the dcmjexe command, or the dcmsusp command (without the /s specification) as a parameter file.
  
• /o
  Specify the full path for the output file. Upon normal completion of the command, the contents of a specified parameter file are output to the output file.
  
• /LC
  Specify ON or OFF to indicate whether the command's processing is to continue after logging off from Windows when Task Scheduler or JP1/AJS is used to execute commands in the background.
  
  • ON
    Continues command processing even after logging off from Windows.
    
  • OFF
    Forcibly terminates command processing once Windows is logged off.
    
  This argument is effective when the command is executed from a service under any of the following OSs:
  
  • Windows NT 4.0
  • Windows 2000
  • Windows XP
  • Windows Server 2003 (excluding Windows Server 2003 (IPF))
  Do not specify /LC ON when you execute the command from the command prompt, because in this case the command is executed as a foreground program.
  You can use a registry setting to specify whether command processing is to continue after Windows is logged off. For details about the registry setting, see the following sections:
  
  • Executing the command in JP1/Software Distribution Manager
    4.6 Registry settings (JP1/Software Distribution Manager) in the manual Setup Guide
    
  • Executing the command in JP1/Software Distribution Client (relay system)
    5.4 Registry settings (JP1/Software Distribution Client (relay system)) in the manual Setup Guide
    
  Note that operation may differ depending on the combination of the /LC specification and the registry setting. For details, see 4.28 Command operation at logoff that depends on a registry setting and logoff option.
  

The table below shows the contents of the parameter file for the dcmrtry command. The contents of the parameter file used in this command cannot be specified by using command arguments.

Table 4-18 Contents of the parameter file (dcmrtry command)

Parameter file specification contents		Description	Specification	Command argument
Tag	Parameter
JOB_ATTRIBUTE	job_generator	Job name	X	--
	jobno	Job number	R	--
	job_folder	Job folder path	X	--
	unsuspended	Whether a distribution being suspended exists	X	--

Legend:

R: required.

X: not required (ignored if specified).

--: Cannot be specified in a command argument.

The following explains the return codes that the dcmrtry command may return:

Code	Meaning	Action
0	Re-execution of job started.	None.
1	Unable to open parameter file. Invalid file format.	Check the parameter file specification or coding format.
2	Invalid value in command argument or parameter file.	Check the values in the parameter file.
3	Error during connection to managing server.	Check the version of the managing server.
4	Unable to open output file.	Check the specification for the output file.
5	Communication failure between client and managing server system.	Check the communications settings in the setup for the managing server.
12	Other errors occurred.	Check the event log.

If JP1/Base is linked to manage JP1/Software Distribution users, see 1.3.3 Setting for executing commands.

• In the parameter file, specify the job number that was output to the output file as a result of execution of the dcmcoll (no /s specification), dcminst (no /s specification), dcmjexe, or dcmsusp (no /s specification) command.
• The dcmrtry command cannot be executed if there is an unknown job number for the job to be re-executed. In this case, you should re-execute the applicable job in the Job Status window of the managing server.

The following is an example of re-executing jobs executed using the dcminst command that are waiting for execution or that have ended in error.

(a) Creating a parameter file

In the parameter file, code the job number of the job that was output to the output file from the dcminst command as follows:

If the output file from the dcminst command has been saved, you can specify that file as a parameter file.

JOB_ATTRIBUTE{
job_generator= NETM_INSTALL_2003_12_11_13_34_36
jobno= JB03121113315383
job_folder= \
}

(b) Command execution

If the output file from the dcminst command is saved in C:\Dmbat\out.txt, you can specify the command as follows:

dcmrtry.exe WAIT ERROR /i C:\Dmbat\out.txt /o C:\temp\retryout.txt