Job Management Partner 1/Software Distribution Client Description and User's Guide

[Contents][Glossary][Index][Back][Next]

2.2.4 Creating the files to be specified during packaging

Organization of this subsection
(1) Creating the packaging-information file
(2) Creating the user resource path file
(3) Setting the special file definition file
(4) Creating the installation script file
(5) Creating the UAPs to be started during installation (client services)
(6) Processing executed before and after the installation enabled by generator tools

(1) Creating the packaging-information file

Before you register resources, you need to create the file that describes the information about the resources to be registered (packaging-information file). This subsection describes how to create the packaging-information file.

(a) Rules for creating the packaging-information file

To create the packaging-information file, use a text editor and the same format as the settings file.

The description format of the packaging-information file is as follows:

attribute-name[Figure] value[Figure]

Where, [Figure] indicates a tab code and [Figure] indicates that you should press the Enter key.

attribute-name
Specify the item to be specified in the packaging-information file.

value
Specify the value to be set for an item in the packaging-information file.

Create the packaging-information file according to the following rules.

(b) Syntax of the package-information file

Format
As shown below, attributes that can be specified in the package-information file differ depending on the package type.

For registering Hitachi program products
Group cabinet-ID
PPName program-product-model
[UserName owner-name]
[HostName host-file-name]
[Compress {NO|COMPRESS|PACK}]
[APafterGeneration external-program-processing-after-market-software-installation]
[APWatchTimer monitoring-time-for-external-program-processing-after-
market-software-installation]
[LifeofResource package-storage-period]
[InstallTiming {BOOT|EXECUTE|SHUTDOWN}]
[Recover {YES|NO}]
[BackupDataKeep backup-file-storage-period]

For registering another company's software
Group cabinet-ID
[ResourceName package-ID]
[ProgramName program-name]
[Version version]
[Generation generation]
[HostName host-file-name]
[UserName owner-name]
[Compress {NO|COMPRESS|PACK|COMMON}]
[APbeforeGeneration external-program-processing-before-installation]
[APafterGeneration external-program-processing-after-installation]
[APWatchTimer monitoring-time-for-external-program-processing]
[LifeofResource package-storage-period]
[InstallTiming {BOOT|EXECUTE|SHUTDOWN|UAP}]
[Recover {YES|NO}]

For registering user data and user programs
Group cabinet-ID
ResourceName package-ID
[ProgramName program-name]
[UserName owner-name]
[Version version]
[PrerequisiteVersion prerequisite-version]
[Generation generation-number]
[Comments user-comment]
[HostName host-file-name]
[Compress {NO|COMPRESS|PACK|COMMON}]
[Generator {STANDARD|NETM_DM_GF}]
[APbeforeGeneration external-program-pre-installation-processing]
[APafterGeneration external-program-post-installation-processing]
[APWatchTimer monitoring-time-for-external-program-processing-for-
installation]
[LifeofResource package-storage-period]
[InstallDirectory installation-target-directory]
[OwnerofInstallDirectory directory-owner]
[GroupofInstallDirectory directory-cabinet]
[ModeofInstallDirectory directory-file-mode]
[InstallTiming {BOOT|EXECUTE|SHUTDOWN|UAP}]
[Recover {YES|NO}]
[BackupDataKeep backup-file-storage-period]
[UAPBackupList backup-list-name]

Explanation

Group cabinet-ID ~ <uppercase alphabetic characters or numerics> ((2 characters))
Specify the ID of the cabinet where resources are to be registered. A cabinet can register up to 256 resources. When you create a new cabinet to register resources, specify the ID of the cabinet here so the cabinet is automatically created and resources can be registered. This item must be specified if you do not specify a cabinet ID in the option of the rdsft or rdscm command.
Specify a different cabinet ID for each managing server that registers resources. If you register resources with the same cabinet ID in different managing servers, the packages may not be distributed even if the package names are different when the cabinet ID is the same.

PPName program-product-model
Specify the model of the program product to be registered. To specify multiple program products, delimit them using blanks and enclose the set values between double quotation marks (").
A description example for specifying multiple program products is as follows:
 
PPName P-1642-111 P-1642-421
By using the regular expression of the UNIX operating system, you can simplify the specification method. A specification example using the regular expression is as follows:
  • PPName *
    Specifies all the program products that are registered in a DAT or CD-ROM.
  • PPName P-1642-*
    Specifies all the program products of which names begin with P-1642-.
  • PPName P-1642-??
    Specifies all the program products of which names begin with P-1642- and end with two numbers.
  • PPName P-1642-[1-5]
    Specifies all the program products of which names begin with P-1642- and end with a number between 1 and 5.

ResourceName package-ID ~ <uppercase alphabetic characters, numerics, hyphens, or underscores> ((1 to 44 characters))
Specify the name of the resource to be registered. Specify a name that is unique in the network system. This item must be specified when you register a Hitachi program product or a user program and user data without specifying the package ID in an option of the rdsft or rdscm command. When you register another company's software or an OS patch, you can omit this item. If you omit this item, the package ID is automatically generated.

ProgramName program-name ~ ((1 to 50 characters))
Specify the general name of the resource to be registered. Specify this name if you want a common name besides the package ID. If you do not specify this value, a blank is assumed. For registration of another company's software, if you omit the package ID and program name, the program name is automatically generated.

UserName owner-name ~ ((1 to 14 characters))
Specify the name of the user who owns the resource to be registered. If you do not specify this value, a blank is assumed.

Version version ~ <uppercase alphabetic characters, numerics, or slants> ((1 to 6 characters))
Specify the version of the resource to be registered. For a program product, the version is automatically set. For other resources, set this item to specify dates and for other purposes. If you do not specify this value, 000000 is assumed. For registration of another company's software, if you omit the package ID and version, the version is automatically generated.

PrerequisiteVersion prerequisite-version ~ <uppercase alphabetic characters, numerics, or slants> ((1 to 6 characters))
Specify the prerequisite version when distributing a resource to be registered.
If you specify 000000 as the prerequisite version, the resource is always distributed regardless of the prerequisite version. If you do not specify PrerequisiteVersion, a blank is assumed and the resource is distributed without checking the prerequisite version.
This specification becomes valid when EXECUTE is specified for InstallTiming.

Generation generation-number ~ <uppercase alphabetic characters or numerics> ((4 digits))
Specify the generation number of the resource to be registered. If you do not specify this value, 0000 is assumed.

Comments user-comment ~ ((1 to 64 characters))
Specify the user comment for the resource to be registered. This specification is valid when NETM_DM_GF is set for Generator. Do not insert a new line within a comment. If you do not specify this value, a blank is assumed.

HostName host-file-name ~ <uppercase alphabetic characters, numerics, hyphens, underscores, or periods> ((1 to 20 characters))
Specify the file name of the host file. If you do not specify this value, the resource is registered into the managing server specified in the settings file. To specify a host file name in a client workstation, specify the host file name of the master workstation.
If you do not specify a host file name in the option of the rdsft or rdscm command, the specification in the packaging-information file is validated. The host file name specified in the rdsft or rdscm command takes precedence over the specification in the packaging-information file.

Compress ~ {NO|COMPRESS|PACK|COMMON}
Specify the type of compression for the resource to be registered.
  • NO
    No compression is performed.
  • COMPRESS
    Use the compress command to compress.
  • PACK
    Use the pack command to compress.
  • COMMON
    Compress a shared package.
If the size of a resource is three blocks or smaller, specifying PACK has no effect. If an error occurs during compression, the resource is registered without compression. If you do not specify this value, the type specified in the settings file is validated.

Generator ~ {STANDARD|NETM_DM_GF} <<STANDARD>>
Specify the type of the generator to be started when a package is installed.
  • STANDARD
    Standard generator provided by the JP1/Software Distribution Client services
  • NETM_DM_GF
    Generator provided by the generator tools of JP1/Software Distribution Client

APbeforeGeneration external-program-pre-installation-processing ~ ((1 to 60 characters))
Use the absolute path to specify the external program pre-installation processing which is started before the standard generator executes installation. If you also specify APafterGeneration (external program post-installation processing), the specification value of this item plus the specification value of APafterGeneration must be within 60 characters.
This specification is valid when you specify STANDARD for Generator. When you specify NETM_DM_GF, the external program pre-installation processing is ignored even if it is specified.
By creating the program of the external program pre-installation processing under /NETMRDS/usrcom/ (/opt/NETMDMW/usrcom/ for HP-UX), you can use the relative path to specify this item.
Note the following when you specify the external program pre-installation processing:
  • Up to 18 character strings (arguments) can be specified.
  • Consecutive blanks are treated as a single delimiter.
  • Do not use the characters that have special meaning in shell programs such as >, <, |, &, and $.
  • Single quotation marks (') are not treated as arguments.
  • Double quotation marks (") cannot be specified. However, when you specify a blank in a set value, enclose the entire set value between double quotation marks.
  • Shell variables are invalid since they are treated as character strings.
  • Do not include processing that waits for responses.

APafterGeneration external-program-post-installation-processing or external-program-processing-after-market-software-installation ~ ((1 to 64 characters))
Use the absolute path to specify the external program post-installation processing or the external program processing after market software installation which is started after a package is installed.
This specification is valid when you specify STANDARD for Generator. When you specify NETM_DM_GF, the external program processing for installation is ignored even if it is specified.
When STANDARD is specified for Generator, if you create a program that requires external program processing for installation under the /NETMRDS/usrcom/ directory (or the /opt/NETMDMW/usrcom/ directory in the case of HP-UX), you can specify the program using a relative path.
Note the following when you specify the external program processing for installation:
  • Up to 18 character strings (arguments) can be specified.
  • Consecutive blanks are treated as a single delimiter.
  • Do not use the characters that have special meaning in shell programs such as >, <, |, &, and $.
  • Single quotation marks (') are not treated as arguments.
  • Double quotation marks (") cannot be specified. However, when you specify a blank in a set value, enclose the entire set value between double quotation marks.
  • Shell variables are invalid since they are treated as character strings.
  • Do not include processing that waits for responses.

APWatchTimer monitoring-time-for-external-program-processing-for-installation or external-program-processing-after-market-software-installation ~ <unsigned integer> ((1 to 32767)) <<300>> (unit: seconds)
Specify the period of time (in seconds) to monitor the execution of the external program processing for installation or the external program processing after market software installation. If the external program processing for installation or the external program processing after market software installation is still executing after the specified value, the distribution-destination system executes the next processing without waiting for the end of the previous processing. In this case, the distribution-destination system reports an installation error to the manager server. This specification is validated at each installation timing.

LifeofResource package-storage-period ~ <numerics> ((8 digits))
Use the YYYYMMDD format to specify the time until which the distributed package is stored in the temporary package storehouse of a relay system.
  • YYYY
    Specify the year (YYYY: current year to 2089).
  • MM
    Specify the month using two digits (MM: 01 to 12).
  • DD
    Specify the day using two digits (DD: 01 to 31).
If you omit this value, the number of days to keep the package, which is specified in the settings file, is validated. An error occurs if you specify a date before the registration date.

InstallDirectory installation-target-directory ~ <alphanumerics> ((1 to 64 characters))
Specify the installation target directory of user data or user programs. For a hard disk resource, you can specify this item when you register the resource using the relative path. If the specified directory does not exist in the distribution-destination system, it is created when the package is installed. If the specified directory is not defined or if you omit this specification, the root directory (/) is assumed.

OwnerofInstallDirectory directory-owner ~ <unsigned integer> ((5 digits from 0 to 59999))
Specify the owner using the user number if the directory specified in InstallDirectory does not exist in the distribution-destination system. If the specified owner is not defined or if you omit this specification, root (user number 0) is assumed.

GroupofInstallDirectory directory-cabinet ~ <unsigned integer> ((5 digits from 0 to 59999))
Specify the cabinet if the directory specified in InstallDirectory does not exist in the distribution-destination system. When you specify a directory cabinet, OwnerofInstallDirectory must be specified. If the specified cabinet number is not defined or if you omit this specification, sys (cabinet number 3) is assumed.

ModeofInstallDirectory directory-file-mode ~ <octal number> ((3 digits from 700 to 777)) <<755>>
Specify the file mode of the directory if the directory specified in InstallDirectory does not exist in the distribution-destination system. For the file mode, specify only the permission mode bits using absolute values. When you specify the file mode of a directory, the following items must be specified:
  • OwnerofInstallDirectory
  • GroupofInstallDirectory
  • InstallDirectory

InstallTiming ~ {BOOT|EXECUTE|SHUTDOWN|UAP} <<EXECUTE>>
Specify the occasion to install software.
  • BOOT
    Install a package when the system is started.
  • EXECUTE
    Install a package when the managing server issues a distribution job.
  • SHUTDOWN
    Install a package when the system is stopped.
  • UAP
    A user application program installs a package. You can specify this value only when the distribution-destination system is Windows.
If the package has a daemon process, install the package when the system is started or stopped. The following packages cannot be installed when the system is started. Install them when the system is stopped.
  • Packages that are started before the user_daemon step in the /etc/rc script
  • Packages with the shared library
  • Packages containing the programs that are registered into /etc/inittab with the respawn specification
Some program products cannot be installed at the specified timing because of the attributes of the programs even if BOOT and EXECUTE are specified. In this case, the distribution-destination system installs those program products when the system is stopped.

Recover ~ {YES|NO} <<NO>>
Specify whether to use the recovery facility.
  • YES
    Execute recovery if installation fails when the package is distributed.
  • NO
    Do not execute recovery if installation fails when the package is distributed.
Some program products may not be able to use the recovery facility because of the attributes of the programs. Recovery is not executed even if you specify YES for such program products. In addition, if the distribution-destination system does not have the backup directory, recovery is not executed even if YES is specified.
Socket device files are not recovered. When you write a socket device in the backup list or register a file with the name identical to that of the socket device, do not specify YES for Recover. If recovery is specified in the packaging-information file that registers a socket device, backups are not acquired when packages are distributed and the socket device file is not distributed.
For another company's software, the recovery facility is available for only the HP-UX version of the software.

BackupDataKeep backup-file-storage-period ~ <unsigned integer> ((0 to 999)) <<0>> (unit: days)
When you use the recovery facility at the distribution of packages, specify the number of days to keep the backup if recovery fails or is not executed. This specification is valid when you specify YES for Recover. The backup will be deleted after the number of days specified here from the date of remote installation.
Recovery can be retried while backups are saved. If you specify 0, backups are not saved. Specify 0 for the packages you do not need to retry recovery for.

UAPBackupList backup-list-name ~ <alphanumerics> ((1 to 128 characters))
To acquire a backup for the recovery facility to be executed at the distribution of the next version after a package is distributed, specify the file name of the backup list containing the file and the directory. For details about the backup list, see 7.4.1 Acquiring backups in PART 2. To specify the file name of the backup list, use the absolute path.
This specification is valid when the package is user data or a user program. This specification is validated when the recovery facility is executed at the distribution of the next version after a package is distributed. This specification is invalid if the recovery facility is executed at the distribution of the current package.
If you do not specify this value, only the file and the directory to be overwritten are backed up when the recovery facility is executed at the distribution of the next version.

(2) Creating the user resource path file

For the user resource path file, specify a directory that is registered from the hard disk. Since you can specify multiple directories or files, you can register the files in different directories as a single resource by creating this user resource path file. Use the absolute path to specify a directory or a file. Do not include .. in a path. A creation example of the user resource path file is as follows:

Example:
/users/home
/etc/hosts
/etc/networks

(3) Setting the special file definition file

To register program products using the special file that is not provided by the system as standard, you need to define such a special file in the special file definition file.

(a) Rules for creating the special file definition file

The special file definition file defines the information of each special file. JP1/Software Distribution Client references this file for the information corresponding to the specified special file when registering a program product and accesses the provided medium.

The special files provided by the system as standard are defined in the special file definition file. The directory name of the special file definition file is as follows.

OS LANG environmental variables Directory name
HP-UX ja_JP.SJIS /etc/opt/NETMDMW/rdsprm/ja_JP.SJIS/DEVTYPE
ja_JP.eucJP /etc/opt/NETMDMW/rdsprm/ja_JP.eucJP/DEVTYPE
Other than ja_JP.SJIS, ja_JP.eucJP /etc/opt/NETMDMW/rdsprm/C/DEVTYPE
Solaris ja_JP.PCK /NETMRDS/rdsprm/ja_JP.PCK/DEVTYPE
ja /NETMRDS/rdsprm/ja/DEVTYPE
Other than ja_JP.PCK, ja /NETMRDS/rdsprm/POSIX/DEVTYPE
AIX Ja_JP /NETMRDS/rdsprm/Ja_JP/DEVTYPE
ja_JP /NETMRDS/rdsprm/ja_JP/DEVTYPE
Other than Ja_JP, ja_JP /NETMRDS/rdsprm/En_US/DEVTYPE

(b) Syntax of the special file definition file

The following shows the format and contents of the special file definition file.

special-file-name[Figure] medium-type[Figure] comment[Figure] medium-type[Figure]

Where, [Figure] indicates a tab code and [Figure] indicates that you should press the Enter key.

special-file-name
Use the absolute path from /dev to specify the special file name that corresponds to the tape device or the disk device where the medium containing the program product is to be set.

medium-type
Specify the type of the medium containing the data.

DISC
Floptical disk or MO

TAPE
CMT or DAT

ISO9660
CD-ROM

UNKNOWN
External storage medium other than disks and tapes

ILLEGAL
External storage medium such as tty and the hard disk

comment
Write a comment. If you do not specify a comment, specify "". An error occurs if you specify a blank.

medium-type
Specify the type of medium.

DAT
The medium is a DAT.

CD-R
The medium is a CD-ROM.

OTHER
The medium is other than above.

(c) Creation example

The following is an example of registering software using special file/dev/dsk/c0t5d0, when the provided recording medium is CD-ROM.

/dev/dsk/c0t5d0  ISO9660  NETM/DM/WPP access  CD-R

(d) Notes

(4) Creating the installation script file

You can edit the following files provided by JP1/Software Distribution Client, as the installation script file.

For details on how to specify the installation script file, see the manual for the Windows version of JP1/Software Distribution.

The installation script file can also be created or edited in the managing server. If an installation script file has been created in the managing server, you do not need to create this file during packaging.

(5) Creating the UAPs to be started during installation (client services)

When you use the client services to install packages, you can start desired UAPs before and after the installation. The external program processing for installation is the processing that is started before or after installation of other software, user programs and user data, or OS patches. The external program processing for installation is divided into the external program pre-installation processing and the external program post-installation processing. The external program processing after market software installation is the processing that is started after a Hitachi program product is installed.

(a) External program processing for installation

To use the external program processing for installation:

  1. Create the program of the external program processing for installation.
    Create the external program processing for installation to return the following return codes after the processing:
    Normal end: 0
    Abnormal end: Other than 0
    If the return code indicates an abnormal end, JP1/Software Distribution Client handles it as an installation error. Note the following when you create the external program processing for installation:
    • Do not include spaces in command path names (except for command arguments).
    • The external program processing for installation is started by a user with superuser permissions.
    • Do not include processing that waits for responses.
    • Do not output messages to the standard output and the standard error output.
    • The environment variables are inherited from the ones that are active when JP1/Software Distribution Client is operating.
    • To implement file operations, such as copying files and logging records to a file, in an external program, make sure that the files are specified with their absolute path names.
  2. In the packaging-information file, set the following attributes:
    Generator             STANDARD
APbeforeGeneration   path-name-of-external-program-pre-installation-
processing
APafterGeneration    path-name-of-external-program-post-installation-
processing
    Use the absolute path name to specify the path name of the external program processing for installation. However, if you create the processing under the /NETMRDS/usrcom/ or /opt/NETMDMW/usrcom/ (for HP-UX) directory, you can use the relative path name.

The following is an example of creating the external program processing for installation for the following operation:

Specifying the packaging-information file
Group              A1
ResourceName       DUMMY01
  :
Generator          STANDARD
APbeforeGeneration "/users/bin/install check"
APafterGeneration  "/users/bin/prog1 DUMMY01"
  :

Contents of the external program pre-installation processing
/bin/rm -r /usrdata/WORK
    RTN =$?
    if [ $RTN != 0]
    /bin/echo "Installation preparation failed (deleting
    work file)" >> /haifu/LOG exit $RTN
    fi
    /bin/mkdir /usrdata/WORK
    RTN=$?
    if [ $RTN != 0]
    /bin/echo "Installation preparation failed (creating
    work directory)" >> /haifu/LOG exit $RTN
    fi
    /bin/echo "Installation preparation completed" >>
    /haifu/LOG
    exit 0

Contents of the external program post-installation processing
RESOURCE=$1
/bin/echo 'RESOURCE='$RESOURCE 'TIME=' '/bin/date' > /tmp/$RESOURCE exit 0

(b) External program processing after market software installation

To use the external program processing after market software installation:

  1. Create the program of the external program processing after market software installation and distribute it to the distribution-destination systems.
    Create the external program processing after market software installation to return the following return codes after the processing:
    Normal end: 0
    Abnormal end: Other than 0
    Note the following when you create the external program processing after market software installation:
    • Do not include spaces in command path names (except for command arguments).
    • The external program processing after market software installation is started by a user with superuser permissions.
    • Do not include processing that waits for responses.
    • Do not output messages to the standard output and the standard error output.
    • The environment variables are inherited from the ones that are active when JP1/Software Distribution Client is operating.
    • To implement file operations, such as copying files and logging records to a file, in an external program that will be executed after software installation, make sure that the files are specified with their absolute path names.
  2. In the packaging-information file, set the following attribute:
    APafterGeneration  path-name-of-external-program-processing-
after-market-software-installation
    Use the absolute path name to specify the path name of the external program processing after market software installation. However, if you create the processing under the /NETMRDS/usrcom/ or /opt/NETMDMW/usrcom/ (for HP-UX) directory, you can use the relative path name.

Even if the external program processing after market software installation ends abnormally, the setup of the distributed program product is normally ended.

An example of the external program processing after market software installation is as follows where JP1/Software Distribution Client is distributed and then JP1/Software Distribution Client starts automatically.

Specifying the packaging-information file
Group               P1
PPName              P-1J42-2C92
  :
APafterGeneration   "users/bin/PP install"
  :

Contents of the external program processing after market software installation
/usr/bin/rdsdmse
    RTN=$?
    if [$RTN != 0]
    then
       /bin/echo "Software Distribution failed to start"
>>  /haifu/LOG
       exit $RTN
    fi
    /usr/bin/rdsdmsts -l    #Displays the connection status.
    exit 0

(6) Processing executed before and after the installation enabled by generator tools

When packages are distributed using the manager tools of JP1/Software Distribution Manager, the distribution-destination systems install them using the generator tools. By specifying a UAP at remote installation enabled by the manager tools, the generator tools start the specified UAP before or after the installation.

The generator tools can start the following three types of UAPs:

UAP used for installation
The processing for installing the distributed packages is written in this UAP. Expand and start this UAP in a work directory that differs from the work directory containing packages. The installation using the UAP used for installation is called UAP-based installation.

Linkage file
This file describes the library linking processing to be started after packages are installed. This file reports the result of processing to the managing server. The installation using the linkage file is called installation that requires linkage processing.

End-linked file
This file describes the user-specific processing to be started after packages are installed. This file does not report the result of processing to the managing server. The installation using the end-linked file is called starting end-linked UAP.

To create these UAPs, use commands, the B shell or the C shell as the shell procedure. However, when using C shell, you need to enter the following in the first line, on the first column of the UAP.

#!/bin/csh
    :

Note the following when you create a UAP:

(a) Interface for startup

The generator, which is a generator tool of the distribution-destination system, starts UAPs using the following format.

 
UAP-name interface-file-name name-of-directory-storing-packages

UAP-name
Name of the UAP to be started.

interface-file-name
This parameter uses the full path to store the name of the file (interface file) that stores the information required for installation using the UAP.
Table 2-6 shows the format of the interface file passed by the generator, which is a generator tool. The Remarks column indicates the supplementary explanation of the items. The storage place is /usr/tmp.

Table 2-6 Format of the interface file

Item Type Size (bytes) Remarks
Package ID C 44 -
Version C 8 Stored in the VVRRZZTT format.
Generation number C 4 -
Identifier C 1 -
Packaging date C 6 Stored in the YYMMDD format.
(YY: Last two digits of the year, MM: Month, DD: Day)
Package owner C 14 -
Program name C 50 -
Size C 6 Displayed in units of kilobytes.
Number of FDs C 3 -
Comment C 64 -
User area C 100 -
Installation status C 1 A number indicating the installation status
(1: Before installation, 2: After installation, 3: Installation failed)
Packager type C 1 -
Cabinet C 2 -
Processing result X 4 Any user information such as the result of UAP-based installation (return value) and details about the installation.
Reserved C 716 -

Legend:
-: Not applicable

name-of-directory-storing-packages
This parameter uses the full path to store the name of the directory storing the packages when UAP-based installation is executed. This parameter is not set for installation that requires linkage processing and starting end-linked UAP.

(b) Interface for termination

This paragraph describes the end status set by the UAPs when the UAPs end and the return values acquired by the distribution-destination systems.

End status
When the processing ends, the UAP needs to set one of the following codes as the end status.
When an end status listed in Table 2-7 is output to the log file of the generator tools, a value calculated by subtracting the number of the code from 256 is used.

Table 2-7 End statuses set by UAPs

Code Status (meaning)
0 Normal end
-2 Insufficient disk size
-3 Interface failure
-4 System error
-6 Internal error
-15 Other errors

UAP return values
If an error occurs during the startup of a UAP, the following return values may be set in the log file of the distributor tools in addition to the codes in Table 2-7.

Table 2-8 UAP return values

Return value Phenomenon
17 The specified UAP does not exist.
18 UAP monitoring time is exceeded.
19 Internal error
20 System error
21 Interruption due to a signal

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.