Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 Distribution Function Administration Guide


14.19.20 USER_PROGRAM_INSTALLATION_CONDITIONS (specifying external programs)

In the USER_PROGRAM_INSTALLATION_CONDITIONS tag, specify the external programs to be started on managed computers before and after package installation and when an installation error occurs. This tag is used for the dcmcoll, dcmpack, and dcmstsw commands.

The following table shows the parameters that can be specified, and their corresponding command arguments:

Parameter

Content

Command argument

external_program_executed_before_installation#1

External program to be started before installation

/b external-program-to-be-started-before-installation

external_program_executed_after_installation

External program to be started after installation

/a external-program-to-be-started-after-installation

external_program_error_handler#2

External program to be started at installation error

/e external-program-to-be-started-at-installation-error

external_program_handler

External program to be started

/ep external-program-to-be-started

exit#2

How to report the processing result of external program

/rbR, /rbM, /raR, /raM, /reR, /reM

action#2

Action to take when processing result is error

/ybC, /ybS, /yaC, /yaS

wait#2

Monitoring method

/wbU, /wbT, /wbG, /waU, /waT, /waG, /weU, /weY

timeout

  • Monitoring time

  • Maximum execution period (for the dcmstsw command)

  • /n monitoring-time

  • /wt maximum-execution-period (for the dcmstsw command)

wait_code

Monitoring code

/wc monitoring-code

#1

For packages to be distributed to UNIX computers, this parameter is ignored if you specify the installation_date_and_time parameter for the SCHEDULE tag at the same time.

#2

For packages to be distributed to UNIX computers, this parameter is ignored even if it is specified.

Specify the programs that do not have a GUI as the external programs to be started. Even when a program having a GUI is started, the program will not display any window or dialog box.

Also, do not specify a 16-bit application program as an external program to be started. If an attempt is made to remotely install a package (for which a 16-bit application program is specified as an external program to be started) in background installation mode on a Windows computer, the Windows computer will hang up.

Organization of this subsection

(1) Format

USER_PROGRAM_INSTALLATION_CONDITIONS{
{
external_program_executed_before_installation=
external-program-to-be-started-before-installation
exit=how-to-report-the-processing-result-of-external-program
action=action-to-take-when-processing-result-is-error
wait=monitoring-method (U, T, or G)
}
{
external_program_executed_after_installation=
external-program-to-be-started-after-installation
exit=how-to-report-the-processing-result-of-external-program
action=action-to-take-when-processing-result-is-error
wait=monitoring-method (U, T, or G)
}
{
external_program_error_handler=
external-program-to-be-started-at-installation-error
exit=how-to-report-the-processing-result-of-external-program
wait=monitoring-method (U or Y)
timeout=monitoring-time
}
{
external_program_handler=
external-program-to-be-started
timeout=maximum-execution-period
wait_code=monitoring-code
}
}

(2) Description

(3) Notes

(a) Notes on starting external programs on UNIX computers

Note the following when using the dcmpack command to set the startup of external programs for packages to be distributed to UNIX computers:

  • Unlike packages for Windows, you cannot specify the external_program_error_handler, exit, action, or wait parameter.

  • For the external_program_executed_before_installation and external_program_executed_after_installation parameters, the path specification method for external programs differs depending on whether the installation_date_and_time parameter is specified for the SCHEDULE tag.

  • Do not use characters that have special meanings in shell programs, such as <, >, |, &, and $.

    The following table describes differences in the path specification method when installation date/time is specified and not specified:

    "installation date/time" specification

    Path specification method for external programs to be started

    external_program_executed_before_installation

    external_program_executed_after_installation

    Specified

    You cannot specify external programs.

    • Specify no more than 40 single-byte characters for a path.

    • You cannot specify a path containing spaces.

    • If the path to the post-processing program contains arguments, enclose the entire part of the path and arguments in double quotation marks (").

    • If the argument contains spaces, enclose the argument including spaces in single quotation marks (').

    Not specified

    • If you specify only external_program_executed_before_installation, specify no more than 60 single-byte characters.

    • If you specify only external_program_executed_after_installation, specify no more than 64 single-byte characters.

    • If you specify both external_program_executed_before_installation and external_program_executed_after_installation, specify no more than 60 single-byte characters for the paths to both external programs.

    • You can specify up to 18 strings (arguments).

    • Successive spaces are treated as a single delimiter.

    • Single quotation marks (') are not treated as arguments.

    • Shell variables are invalid because they are treated as strings.

    • Do not specify a process that waits for a response.

Note the following when using the dcmcoll command to set the startup of external programs on UNIX computers:

  • Unlike Windows computers, you cannot specify the external_program_error_handler parameter.

  • For the path to the external program to be started, specify no more than 64 single-byte characters. If you specify more than 64 characters, only the first 64 characters are valid.

  • The path to the external program to be started cannot contain spaces.

  • You cannot specify arguments in the external program to be started.

If the path specification method is incorrect, packaging and jobs can be executed, but external programs will not be started on the destination UNIX computers. In this case, note that jobs do not produce an error but terminate normally.