This command packages user data or user programs for the managing server (JP1/Software Distribution Manager or JP1/Software Distribution Client (relay system)).

Program products cannot be packaged.

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

• /k
  Specify the password for the packaging of software for the managing server.
  

  Packaging for the Windows managing server

  Specify the password that was specified during the creation of a relational database in the managing server.

  Packaging for the UNIX managing server

  Specify the package upload password for the UNIX managing server.

• /i
  Specify the full path for the parameter file.
  
• /o
  Specify the full path for the output file. Upon normal termination of the command, attributes of the package that was created are written into a specified output file. You can use the resulting output file as a parameter file for the dcminst, dcmpkget, and dcmpkrm commands.
  The default is not to create an 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
    
  • Executing the command in JP1/Software Distribution Client (client)
    6.3 Registry settings (JP1/Software Distribution Client (client)) 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.
  

You can also use command arguments to specify the contents of the parameter file used in this command. The table below shows the correspondence between the contents of a parameter file and the command arguments.

Table 4-14 Correspondence between parameter file contents and arguments (dcmpack command)

Parameter file specification contents		Description	Specification	Command argument
Tag	Parameter
PACKAGING_SOURCE	file_path	File to be packaged	O	/P value
	base_fullpath	Package base directory	R	/B value
PACKAGING_INFORMATION	package_name	Package name	R	/p value
	package_id	Package ID	R	/I value
	version_revision	Version/revision	R	/v value
	generation	Generation	R	/G value
	cabinet_name	Cabinet name	R	/c value
	cabinet_id	Cabinet ID	R	/C value
	package_code	Code type	X	--
SYSTEM_CONDITIONS	directory	Installation directory	O	/D value
	condition	System condition	O#1, #2	/O value
SOFTWARE_CONDITIONS	condition	Software condition	O#1, #2	/l value
FILE_PROPERTIES	permission	Restoration of file-access permission	O	/qY or /qN#3
SCHEDULE	expiration_date	Package expiration date in the relay system	O	/x value
	expiration_days	Package expiration days in the relay system	O	/ed value
	installation_date_and_time	Installation date and time	O	/d value
	installation_timing	Installation timing	O	/tS or /tN
INSTALLATION_METHOD	installation_mode	Installation mode	O	/mB or /mG
OPTION	compress	Compression, yes/no	O	/uY or /uN
	compress_type	Compression method	O	/ctN or /ctH#4
	restore	Restore operations during version upgrades	O	/RY or /RN
	encipher	Encryption yes/no	O#5	/encY or /encN
	reboot	Post-installation reboot	O	/reboot
	processing_dialog	Dialog display during installation	O#1	/procS, /procY, or /procN
USER_PROGRAM_INSTALLATION_CONDITIONS	external_program_executed_before_installation#6	External program that is started before installation	O	/b value
	external_program_executed_after_installation	External program that is started after installation	O	/a value
	external_program_error_handler#7	External program that is started upon an installation error	O	/e value
	external_program_handler	External program handler	X	--
	exit#7	Results-notification method	O	/rbR, /rbM, /raR, /raM, /reR, or /reM
	action#7	Disposition of processing error	O	/yaC, /yaS, /ybC, or /ybS
	wait#7	Notification method for external program processing results	O	/wbU, /wbT, /wbG, /waU, /waT, /waG, /weU, or /weY
	timeout	Monitoring time	O#8	/n value
	wait_code	Wait code	X	--
SCRIPTS	installation_script	Installation script path	O#1, #9	/Z value

Legend:

R: required.

O: optional.

X: not required (ignored if specified).

--: Cannot be specified in a command argument.

#1

Not specifiable with packages that are distributed to UNIX clients.

#2

If multiple system and software conditions are specified, the package is installed when all the conditions are met. When specifying in terms of command arguments, you can specify a total of 10 /O and /l.

#3

Specify /qN to distribute packages to UNIX clients.

#4

Specify /ctN to compress packages for distribution to UNIX clients.

#5

This parameter requires the installation of JP1/Software Distribution Encryption Option.

#6

For a package that is distributed to UNIX clients, this parameter, if specified with the installation_date_and_time parameter of the SCHEDULE tag, is ignored.

#7

This parameter is ignored if specified with packages distributed to UNIX clients.

#8

Any U specified in wait (specifying /wbU, /waU, and /weU in command arguments) is ignored.

#9

If this item is specified, any information that applies to the SYSTEM_CONDITIONS tag, the SOFTWARE_CONDITIONS tag, and the USER_PROGRAM_INSTALLATION_CONDITIONS tag is ignored.

The following shows the format of the command when you specify the command by using arguments only instead of using a parameter file.

dcmpack.exe [/k password]
              [/P file-to-be-packaged]
               /B package-base-directory
               /p package-name /I package-ID
               /v version/revision /G generation
               /c cabinet-name /C cabinet-ID
              [/D installation-directory]
              [/0 system-condition] [/l software-condition]
              [{/qY|/qN}]
              [/x package-expiration-date-in-the-relay-system]
              [/ed package-expiration-days-in-the-relay-system]
              [/d installation-date-and-time] [ {/tS|/tN}]
              [{/uY | /uN}] [ {/RY | /RN}] [ {/encY | /encN}]
              [/reboot] [ {/procS | /procY | /procN}]
              [/b external-program-that-is-started-before-installation
              [{/rbR | /rbM}] [ {/ybC | /ybS}]
              [{/wbU | /wbT | /wbG}] [ /n monitoring-time] ]
              [/a external-program-that-is-started-after-installation
              [{/raR | /raM}]
              [{/yaC | /yaS}] [ {/waU | /waT | /waG}]
              [/n monitoring-time] ]
              [/e external-program-that-is-started-on-an-installation-error
              [{/reR | /reM}] [ {/weU | /weY}]
              [/n monitoring-time] ]
              [/Z installation-script-path]
              [/o result-output-file-name]
              [/LC {ON|OFF}]

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

Code	Meaning	Action
0	Normal termination.	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 settings for the command argument or parameter file.
3	Error during connection to managing server.	Check the settings or communications environment for the PC on which the packaging is to be executed.
4	Unable to create output file, or automatic counting of versions/revisions and generations using a reserved word failed; however, registration of package is successful.	Check the path specifying the file to be packaged.
5	Connection to managing server failed.	Check to see if the managing server or the relational database has stopped.
6	Data send/receive to and from managing server failed.	Check the communications environment.
7	One of the following: File or directory to be packaged does not exist. Number of files or directories to be packaged exceeds the maximum value.	Check the path for the file or directory to be packaged. Reduce the number of files or directories to be packaged.
9	The package to be packaged is already packaged.	Change one of the following items and then retry the packaging process: Cabinet ID Package ID Version number Generation
12	Other errors occurred.	Check the event log.
13	Invalid password.	Check the password.
14	Automatic counting of versions/revisions or generations produced a result that exceeds the maximum number of digits that can be specified; registration of package failed.	Check the settings for the reserved words for versions/revisions, and generation.

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

• Specifying a cabinet
  
  • Specifying a non-existent cabinet ID in a parameter file or a command argument creates a new cabinet.
  • If multiple combinations of different cabinet IDs and cabinet names are specified, the second and higher packages are stored in the cabinet that was specified in terms of a cabinet ID. No error occurs.
• Number of package specifications
  For each execution of the dcmpack command, you can specify one package (as is the case when the command argument is used).
  
• Automatic counting of versions/revisions and generations
  By using reserved words, you can execute the automatic counting of versions/revisions and generations. In this case, a specification from a parameter file and that from a command argument can produce different operations, as follows:
  

  Specifying from a parameter file

  The initial count-up value is reset when the dcmpack command is executed and the new value is overwritten on the parameter file. Re-executing the command using the same parameter file commences the counting process on a continued basis.

  Specifying from a command argument

  Executing the dcmpack command does not reset the initial value. Therefore, each time the command is executed, the counting is performed from the initial value.

• Connection target for the dcmpack command
  The user who has update permission for the HKEY_LOCAL_MACHINE registry starts Packager and the connected server becomes the connection target. To change the connection target, the user who has update permission for the HKEY_LOCAL_MACHINE registry must start Packager, change the connection target, and then execute the dcmpack command.
  
• When the parameter file is not used
  
  • Do not use a path containing a space for an external program.
  • If the distribution destination is WS (UNIX system), specify any drive as the drive of the installation destination directory or the directory to which external program is stored. During distribution, however, the specified drive is ignored and the package is distributed according to the directory specification. For example, c: would be ignored in the following case:
    Specification example: c:/user/tmp
    If you use the backslash (\) for the directory delimiter, you do not need to specify a drive.
    Specification example: \user\tmp
    
• Notes about using an installation-script file
  
  • The dcmpack command does not perform a syntax check on the installation-script file that was incorporated by the specification of the SCRIPTS tag of the parameter file.
  • Using an installation-script file nullifies any specification of system conditions (except for the installation directory), software conditions, and the start of an external program.
• Notes about not using an installation-script file
  If an installation-script file is not used, and system conditions, software conditions, and the start of an external program are specified simultaneously, the start of the external program is coded in the installation-script file. However, any results-notification method, processing error handling, monitoring method, or timeout for the external program specified is nullified.
  
• Notes about installing a new packager
  If a new Packager is installed, start Packager, and then specify the server before executing the dcmpack command.
  
• Notes about installing a package in the background installation mode
  Do not specify a drive on a network drive for the installation directory.
  

The following is an example of packaging a file under the C:\Finance\data0401 directory as follows:

• Package name
  Finance Data 2003 4
  
• Storage cabinet name
  FCAB01
  

(a) Creating a parameter file

You can create a parameter file as follows:

** dcmpack Parameter File Sample
 
PACKAGING_SOURCE{
file_path=FD200304.dat
base_fullpath= C:\Finance\data0401
}
PACKAGING_INFORMATION
{
package_name=Finance Data 2003 4
package_id=FD200304
version_revision=000001
generation=0000
cabinet_name=FCAB01
cabinet_id=F1
package_code=P
}
SYSTEM_CONDITIONS{
condition=H:c>300
condition=C = PowerPC
directory=C:\Finance
}
USER_PROGRAM_INSTALLATION_CONDITIONS
{
external_program_executed_after_installation = C:\Dmbat\app\normal_exit.exe
}

(b) Command execution

When saving the parameter file in a file named C:\Dmbat\para.txt, code the command as follows:

Dcmpack.exe /i C:\Dmbat\para.txt