5.8.2 Items set in the operating-environment settings file
- Organization of this subsection
-
-
(3) Retry count and retry interval for using a socket to start a resident server for TCP/IP
-
(5) Controlling outputting messages to /dev/console as well as MAIN.LOGF
-
(6) Time period for checking whether a resident server for TCP/IP was deactivated by a socket
-
(8) Removing restrictions on the paths for package registration and collection
-
(9) Size of another company's software installation log file
-
(13) Reporting of inventory information to a higher-level system during a system change
-
(14) Reporting of information on another company's software in file set units
-
(15) Reporting inventory information to a higher-level system during the initial polling
-
(18) Time to wait until a forced installation stop when the system is starting or stopping
(1) Locale for messages
For the locale for the messages output by JP1/IT Desktop Management 2 - Agent, specify the language in the LANG environment variable and the time zone in the TZ environment variable. The following is an example for setting the locale.
LANG=C TZ=JST-9 export LANG TZ
An English environment is set by default. Specify the language only when you need to change the default environment to a different environment. Note that the messages output to syslog are output in English. You cannot change the output language.
(2) Retry count for sending processing results
Use this item to set the number of retries to be performed if the transmission of the processing results to the managing server fails. See below for details on how to specify this item. You do not need to use the export statement. Do not specify this item if CLIENT is specified for WorkstationType in the settings file.
SNDCNT=retry-count
In retry-count, specify a value in the range from 0 to 9. If you do not specify this item, retries are performed until the transmissions are completed. Transmissions are retried every minute.
If the number of retries exceeds the specified value, the KDDM0541-W message is output to syslog and the MAIN.LOGF log file. If this message has been output, correct the error, and then perform either of the operations below. Transmissions are retried every minute or at the time interval specified for WatchTimeofStatus in the settings file of JP1/IT Desktop Management 2 - Agent. If a value greater than or equal to 2 or greater is specified, that value becomes the number of retries to be performed.
- Operation from the managing server:
-
Executes a job for an end workstation.
- Processing by the end workstation:
-
-
For systems other than HP-UX
rdsft -a [-h host-name-of-the-higher-level-system]
-
For HP-UX
/opt/NETMDMW/bin/rdsft -a [-h host-name-of-the-higher-level-system]
-
(3) Retry count and retry interval for using a socket to start a resident server for TCP/IP
You can specify the retry count and retry interval for using a socket to start a resident server for TCP/IP as follows:
BINDRETRY=retry-count BINDRETRYINTERVAL=retry-interval
In retry-count, specify a value from 1 to 256. The default is 20. In retry-interval, specify a value from 1 to 300 in seconds. The default is 60.
(4) No-response timeout
You can use the COMWAT environment variable as follows to set the timeout for no-response in the communication between Agent and the higher system.
COMWAT=timeout
In timeout, set a value from 0 to 2,147,483,647 in seconds. The default is 60.
- Important
-
For distribution of package with large size, refrain from specifying 0 to the value of COMWAT.
(5) Controlling outputting messages to /dev/console as well as MAIN.LOGF
If JP1/IT Desktop Management 2 - Agent fails to output a message to the standard output, specify the following to output a message to the console:
CONSOLEMSG=YES
If you specify NO, the message is not output. The default is NO.
If you specify YES, processing in JP1/IT Desktop Management 2 - Agent might be delayed because of a console lock. We recommend specifying NO.
Even if NO is specified, the content of the message is output to message log files and syslog files for client services.
(6) Time period for checking whether a resident server for TCP/IP was deactivated by a socket
In the case of an end workstation, it is possible to check when a resident server for TCP/IP is deactivated by a socket.
When you want to check whether a resident server for TCP/IP was deactivated by a socket, use the variable below to specify the no-communication period. If the no-communication status lasts for the specified period, JP1/IT Desktop Management 2 - Agent assumes that the resident server for TCP/IP was deactivated by a socket.
SOCKETLOOP=time-period
In time-period, you can specify a value from 300 to 65,535 in seconds. The default is 300.
(7) Executing all regular commands
If you want to run regular commands, add the following line to the operating-environment settings file.
REGULARJOB_NOSERVER_NOEXEC=NO
You do not need to use the statement like "export REGULARJOB_NOSERVER_NOEXEC".
(8) Removing restrictions on the paths for package registration and collection
By default, the following cannot be specified as paths for packaging and file collection:
-
/
-
/usr, /bin, /dev, /ofis, /2050, /3050 (including sub-directories and files when collecting a file)
-
/etc (including sub-directories when collecting a file)
To allow these paths to be used, enter the following setting:
PROHIBITPATH=NO
As #PROHIBITPATH=NO is specified in the model file, delete the leading # symbol to enable the value. You do not need to use the export statement. If you omit this value, YES is assumed and the paths prohibited by default cannot be used for packaging or collection.
(9) Size of another company's software installation log file
When another company's software is distributed, installation information is output to the another company's software installation log file (ISVSOFT.LOGF). The maximum size of this file is set as shown below:
MAXSIZE_ISV_LOGF=size
In size, specify the number of kilobytes in the range from 10,240 to 2,097,152. The default is 10,240 (KB).
If the size of the ISVSOFT.LOGF file exceeds the maximum, the information currently stored in the file is moved to the backup file, ISVSOFT.LOGF.bak, and new information is output to ISVSOFT.LOGF.
(10) Host name of the local system
Specify in the following format the local system's host name reported by the facility for automatically registering the system configuration:
DMHOSTNAME=host-name
In host-name, specify a host name from which an address can be resolved. You can use a maximum of 64 alphanumeric characters, including hyphens (-), underscores (_), and periods (.) to specify the host name. If you omit this entry or specify an invalid value, the host name acquired by the hostname command is used.
Before changing this setting, make sure that no jobs are being executed.
- Important
-
The value of DMHOSTNAME specified in the operating-environment settings file is only valid for the client services. For the distributor tools and the generator tools, the host name displayed by the hostname command is used as the local host name.
(11) IP address of the local system
Specify in the following format the local system's IP address reported by the facility for automatically registering the system configuration:
DMIPADDR=IP-address
In IP-address, specify an IP address with which communication is possible.
If you omit this entry, the system assumes an IP address as follows:
-
When DMHOSTNAME is specified: The IP address for the host name specified in DMHOSTNAME
-
When DMHOSTNAME is also omitted: The IP address for the host name that can be acquired by the hostname command
Before changing this setting, make sure that no jobs are being executed.
(12) Process monitoring interval
Using the format shown below, specify the interval at which to check whether or not the rdsregular process is alive.
PROCESSCHKINTERVAL=monitoring-interval
Specify the monitoring interval as a value from 0 to 65,535 in seconds. If 0 is specified, monitoring of the rdsregular process is not performed. The default value is 10 seconds. Note that there is a 10-second error in the monitoring interval.
(13) Reporting of inventory information to a higher-level system during a system change
When a system change is detected and it is necessary to automatically report the system information and software information to a higher-level system, specify the following:
REALTIME_INVENTORY=YES
If this specification is omitted, NO is assumed and system changes are not detected.
When you specify YES here, you must also specify the following:
-
Client services settings file
EnableMultiServer NO
-
Operating-environment settings file
FILESET_MANAGEMENT=YES (for AIX only)
(14) Reporting of information on another company's software in file set units
In AIX, to report the information on another company's software in file set units, specify the following:
FILESET_MANAGEMENT=YES
If this specification is omitted, NO is assumed and the software information is reported in package units. This specification is valid only in AIX.
If you change this specification, file set information and package information will coexist. To avoid this, first delete the software on the managing server and then change the setting.
(15) Reporting inventory information to a higher-level system during the initial polling
To report the system information and software information to a higher-level system at the time of the initial polling, specify the following:
INVENTORY_UPLOAD=YES
If you specify NO, the information is not reported. The default is YES.
If YES is specified, you must also specify the following:
-
Client services settings file
EnableMultiServer NO
(16) Converting the character encoding of package information and information about collected resources
You can use Japanese to enter package information such as the package name. To prevent corrupted characters in package information such as the package name when the language environment used is different from that of the managing server and distribution-destination system, specify the following for the packager and distribution-destination system:
CONVERT_CHARSET=SJIS
The specification is valid in the following cases:
-
When Shift JIS encoding is used for the managing server and EUC encoding or UTF-8 encoding is used for the language environment of the packager, you want to display the package information such as package names correctly without corrupted characters.
-
When Shift JIS encoding is used for the managing server and EUC encoding or UTF-8 encoding is used for the language environment of the distribution-destination system, you want to distribute file names and directory names correctly without corrupted characters.
-
When Shift JIS encoding is used for the distribution-destination system and EUC encoding or UTF-8 encoding is used for the language environment of the packager, you want to distribute file names and directory names correctly without corrupted characters.
The items converted by this function are listed below.
(a) If this function is enabled for the packager
At packaging, the following items of package information are converted from the language environment of the packager to Shift JIS encoding:
-
Program name
-
Owner name
-
Name of an installation directory
-
User comments
-
External program processing before installation
-
External program processing after installation
-
Names of files and directories
(b) If this function is enabled for the distribution-destination system
At the time of distributing the resources, the following items of package information are converted from Shift JIS encoding to the language environment of the distribution-destination system:
-
Program name
-
Owner name
-
Name of an installation directory
-
User comments
-
External program processing before installation
-
External program processing after installation
-
Names of files and directories
-
Names of linkage files
-
Name of the UAP used for installation
-
Name of the end-linked file
At the time of collecting the resources, the following items of collected resource information are converted from Shift JIS encoding to the language environment of the distribution-destination system:
-
Names of resource files
-
External program processing before collection
-
External program processing after collection
The following items of collected resource information are converted from the language environment of the distribution-destination system to Shift JIS encoding:
-
Names of files and directories
If this specification is omitted, package attribute information and collection information, for which Japanese can be used for input, will not be converted.
(17) Path name of a temporary work directory
To change the path name of a temporary work directory to be used for processing in JP1/IT Desktop Management 2 - Agent, specify the following:
DMTMPDIR=path-name-of-a-temporary-work-directory
You can specify a maximum of 128 alphanumeric characters, excluding spaces, for the path name of a temporary work directory. If this specification is omitted, or a specified directory does not exist, the following directories are assumed:
-
For systems other than HP-UX: /NETMRDS/WORK/tmp
-
For HP-UX: /var/opt/NETMDMW/WORK/tmp
(18) Time to wait until a forced installation stop when the system is starting or stopping
To avoid delaying the startup or shutdown of an OS because of the time taken for installation processing while the system is starting or stopping, you can forcibly stop installation while the system is starting or stopping. To forcibly stop installation while the system is starting or stopping, specify the time until installation is forcibly stopped as follows:
FORCESTOP_WAITTIME=wait-time-until-forced-stop
Specify the time to wait until the forced stop in minutes in the range from 0 to 1440. If you specify 0, installation will not be forcibly stopped. If this specification is omitted or the specified value is invalid, 0 is assumed, and installation will not be forcibly stopped.
If installation is forcibly stopped, a message that indicates that the process has been stopped might be displayed on the window.
(19) Expansion of acquired software information
Specify the following to expand the acquired software information.
EXPAND_SOFTWARE_INFORMATION=YES
The item above can only be set for Linux, Solaris (only for Solaris11 or later), or AIX. If omitted, NO is assumed and standard software information is acquired. To set this to YES, you need to specify the following as well.
-
jdn_manager_config.conf file of JP1 / IT Desktop Management 2 - Manager Expand_LinuxSoftwareInformation=YES
For details on expansion of software information, see 6.2 Acquiring software information.