This command executes the job defined in a parameter file. Only one job per JOB_ATTRIBUTE tag can be executed.

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

• /i
  Specify the full path for the parameter file to be used.
  You can also use the output file from the dcminst command (with the /s specification), the dcmcoll command (with the /s specification), or the dcmsusp command (with the /s specification) as a parameter file.
  
• /o
  Specify the full path for the output file. The following items are output to the specified output file upon normal completion of the command, overwriting any previously existing output file.
  
  • Job name
  • Job number
  • Job storage folder path
  The job number (value of jobno) identifies the job that has been started. When deleting this job or verifying its execution status, you should code the value of jobno in the parameter file. You can use the output file as a parameter file for the dcmjbrm, dcmrtry, dcmstat, and dcmstsw commands.
  
• /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.
  

Although the dcmjexe command requires a parameter file, you can also use command arguments to specify some of the parameter file contents used in this command. The table below shows the correspondence between the contents of a parameter file and the command arguments.

Table 4-13 Correspondence between parameter file contents and arguments (dcmjexe command)

Parameter file specification contents		Description	Specification	Command argument
Tag	Parameter
JOB_ATTRIBUTE	job_generator	Job name	R	--
	jobno	Job number	X	--
	job_folder	Job folder path	O#	--
	unsuspended	Whether a distribution being suspended exists	X	--
JOB_SCHEDULE	job_entry_date	Job registration date and time	O	/jst value
	job_execution_date	Job execution date and time	O	/jsx value
	job_expiration_date	Job execution limit	O	/jsp value

Legend:

R: required.

O: optional.

X: not required (ignored if specified).

--: Cannot be specified in a command argument.

#

By default, the dcmjexe command executes a job by searching all the folders or files that lie below the root folder.

To specify the job registration date and time, job execution date and time, and job execution time limit by using the command arguments, code the command in the following format:

dcmjexe.exe /i parameter-file-name /o result-output-file-name
            [/jst job-registration-date-and-time][/jsx job-execution-date-and-time]
            [/jsp job-execution-time-limit] [/LC {ON|OFF}]

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

Code	Meaning	Action
0	Managing server has started job.	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. A job may have been started. Check the job status.
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.

The following is an example of executing an invoice-file-0001-collection job saved in the batch-definition of the managing server system folder.

(a) Creating a parameter file

Code the folder in which the job to be executed is saved, and the job name, in the parameter file as follows, and save the parameter file under any name:

** dcmjexe Parameter File Sample
 
JOB_ATTRIBUTE{
job_generator= invoice-file-0001-collection
job_folder= \batch-definition
}

(b) Command execution

When saving the parameter file in a file named C:\Dmbat\dcmjexe.txt and acquiring an output file in C:\Dmbat\out.txt, code the following specification:

dcmjexe.exe /i C:\Dmbat\dcmjexe.txt /o C:\Dmbat\out.txt

(c) Checking the output file

Upon normal completion of the command, the job name of the job that was started, the job number, and the job storage folder path are output to the C:\Dmbat\out.txt file as follows:

JOB_ATTRIBUTE{
job_generator= invoice-file-0001-collection
jobno= JB03121113315383
job_folder= \batch-definition
}