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

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

6.8.2 Items set in the operating-environment settings file

Organization of this subsection
(1) Locale for messages
(2) Maximum number of packages for each group
(3) Automatic registration of the system configuration
(4) Retry count for sending processing results
(5) Interval for monitoring scheduled packages
(6) Retry count and retry interval for using a socket to start a resident server for TCP/IP
(7) No-response timeout
(8) Controlling outputting messages to /dev/console as well as MAIN.LOGF
(9) Logging the information that the same package has already been stored when storing a package in the temporary package storehouse
(10) Time period for checking whether a resident server for TCP/IP was deactivated by a socket
(11) Executing all periodic jobs
(12) Removing restrictions on the paths for package registration and collection
(13) Size of another company's software installation log file
(14) Clearing the settings of the send and receive socket buffer sizes
(15) Host address of the local system
(16) IP address of the local system
(17) Using host IDs to manage clients
(18) Automatically deleting jobs when system reconfigured
(19) Process monitoring interval
(20) Using the JP1/Software Distribution system configuration to resolve addresses
(21) Timing for sending the result file to the server
(22) Reporting of inventory information to a higher-level system during a system change
(23) Reporting of information on another company's software in file set units
(24) Reporting of inventory information to a higher-level system during automatic registration of system configuration

(1) Locale for messages

For the locale for the messages that JP1/Software Distribution Client may output, 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

(2) Maximum number of packages for each group

The maximum number of packages that you can store in the package storehouse for each group is set in the MAXRSC environment variable in the following format:

MAXRSC=maximum-number-of-packages-for-each-group

As the maximum number of packages for each group, you can specify 256 to 5,000. If you do not specify the MAXRSC environment variable, 256 is implicitly specified as the maximum number of packages for each group.

(3) Automatic registration of the system configuration

To automatically register the system configuration for a relay system or end workstation, set the environment variable SYSCNS as shown below. You do not need to use the export statement.

SYSCNS=YES

As #SYSCNS=YES is specified in the model file, delete the leading # symbol to enable the value.

You need not specify this item if one of the following conditions is satisfied:

If you specify automatic registration after the relay system or distribution-destination system has been set up, the system configuration is not reported to the managing server. In this case, to automatically register the system configuration, perform the following steps:

[Figure] For a relay system

Operation for automatically registering the relay system configuration:
  • For systems other than HP-UX
    rdssnd -q
    /NETMRDS/COM/rdskillsrv
    rm /NETMRDS/rdsprm/NS000000
    /NETMRDS/COM/rdsstart
    rdsft -a
  • For HP-UX
    /opt/NETMDMW/bin/rdssnd -q
    /opt/NETMDMW/lbin/rdskillsrv
    rm /var/opt/NETMDMW/rdsprm/NS000000
    /opt/NETMDMW/lbin/rdsstart
    /opt/NETMDMW/bin/rdsft -a

Operation for automatically registering the distribution-destination system configuration:
From the managing server, execute the Get system configuration information job on the relay systems.

[Figure] For an end workstation
  • For systems other than HP-UX
    /NETMRDS/COM/rdssnde -q
    /NETMRDS/COM/rdskillsrv
    rm /NETMRDS/rdsprm/NS000000
    /NETMRDS/COM/rdsstart
    rdsft -a
  • For HP-UX
    /opt/NETMDMW/lbin/rdssnde -q
    /opt/NETMDMW/lbin/rdskillsrv
    rm /var/opt/NETMDMW/rdsprm/NS000000
    /opt/NETMDMW/lbin/rdsstart
    /opt/NETMDMW/bin/rdsft -a

(4) 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. The following shows 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, you can specify 0 to 9. If you do not specify this item, retries are performed until the transmission is completed. For an end workstation, transmission is retried every minute. In all other cases, transmission is retried at the time interval specified for WatchTimeofStatus in the settings file of JP1/Software Distribution Client.

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 following operations. In this case also, transmission is retried every minute or at the time interval specified for WatchTimeofStatus in the settings file of JP1/Software Distribution Client. If 2 or greater is specified, that value becomes the number of retries to be performed.

Operation from the managing server:
Executes a job for a relay system or end workstation.

Processing by the relay system or end workstation
  • For systems other than HP-UX
    rdsft -a [-h host-file-name or host-name]
  • For HP-UX
    /opt/NETMDMW/bin/rdsft -a [-h host-file-name or host-name]

(5) Interval for monitoring scheduled packages

You can use the GFAUTO environment variable as follows to specify the interval for checking whether the installation date/time for a package has been reached. You do not need to use the export statement.

GFAUTO=monitoring-interval

In monitoring-interval, specify a value from 1 to 32,757 in minutes. If you do not specify this variable, JP1/Software Distribution Client does not monitor the packages scheduled for installation.

The value you specify in this variable is enabled after you restart the system. Note that if you set a very long interval, the difference between the scheduled installation date/time and the actual installation date/time may be very large.

(6) 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.

(7) No-response timeout

You can use the COMWAT environment variable as follows to set the timeout for no-response in the communication between a relay system and a client.

COMWAT=timeout

In timeout, set a value from 0 to 2,147,483,647 in seconds. If 0 is specified for the value, no monitoring is performed. The default is 60.

(8) Controlling outputting messages to /dev/console as well as MAIN.LOGF

If JP1/Software Distribution Client fails to output a message to the standard output, it redirects the message to the console. You can use the following specification to suppress redirecting messages to the console.

CONSOLEMSG=NO

As #CONSOLEMSG=NO is already specified in the model file, delete the leading # symbol to enable this item. You do not need to use the export statement. If you do not specify this variable, CONSOLEMSG=YES is assumed.

(9) Logging the information that the same package has already been stored when storing a package in the temporary package storehouse

If you attempt to store a package in the temporary package storehouse that already contains the same package, you can use the following specification to log the information that the same package has already been stored.

KPMSG=YES

The value YES has already been specified in the model file, so you need only delete the leading pound sign (#) to enable this item. You do not need to use the export statement. If you do not specify this variable, KPMSG=NO is implicitly specified.

(10) Time period for checking whether a resident server for TCP/IP was deactivated by a socket

When you want to check whether a resident server for TCP/IP was deactivated by a socket, use the following variable to specify the no-communication period. If the no-communication status lasts for the specified period, JP1/Software Distribution Client 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.

(11) Executing all periodic jobs

When the higher system changes, the periodic jobs received from the original higher system remain at the distribution-destination system. Nevertheless, the distribution-destination system is set to execute only the periodic jobs received from the current higher system.

To execute all periodic jobs whichever higher system they are received from, specify as follows:

REGULARJOB_NOSERVER_NOEXEC=NO

As #REGULARJOB_NOSERVER_NOEXEC=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 only the periodic jobs from the higher system specified in ManagingHost in the settings file are executed.

If the higher-level relay system of the client workstation is Version 7i or earlier for Windows of JP1/Software Distribution SubManager, you cannot specify YES for this item.

(12) Removing restrictions on the paths for package registration and collection

By default, the following cannot be specified as paths for packaging and file collection:

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.

(13) 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.

(14) Clearing the settings of the send and receive socket buffer sizes

In JP1/Software Distribution, the sizes of the send and receive socket buffers used for intra-system communication have been set separately. The following shows how to clear the settings of these socket buffer sizes in JP1/Software Distribution.

Before you clear the buffer size settings, always verify that the system performance in your environment will not be degraded. When these settings are not cleared, the buffer sizes are fixed at 32,768 bytes. When these settings are cleared, the system defaults are used. In an OS other than HP-UX, the following tuning parameters are used for the system defaults.

OS Type Tuning parameter
Solaris Send tcp_xmit_hiwat
Receive tcp_recv_hiwat
AIX Send tcp_sendspace
Receive tcp_recvspace

(15) Host address 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 32 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.

(16) 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:

Before changing this setting, make sure that no jobs are being executed.

(17) Using host IDs to manage clients

When the Windows version of JP1/Software Distribution Manager is set to use host IDs, jobs can be transferred on the basis of host IDs even if there are duplicate client host names or IP addresses. To use host IDs to transfer jobs, specify the following setting:

CLIENT_KEY=HOSTID

If this specification is omitted, jobs are relayed in the same manner as in Version 08-10 or earlier of JP1/Software Distribution SubManager. That is, jobs are relayed using host names or IP addresses, provided that client host names or IP addresses are not duplicated. When you install JP1/Software Distribution Client for the first time, always specify this setting. After the setting of JP1/Software Distribution Manager is changed to use host IDs for client management, always execute the rdssysmig command to convert the system configuration information of the relay system.

Before changing this setting, make sure that no jobs are being executed.

(18) Automatically deleting jobs when system reconfigured

When clients are removed from the system configuration, the jobs that are to be sent to the clients can also be deleted from the relay system. You can enable this function by specifying the following setting:

CLIENT_CMD=DELETE

This function is disabled if this setting is not specified.

(19) 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.

(20) Using the JP1/Software Distribution system configuration to resolve addresses

To use the JP1/Software Distribution system configuration to resolve addresses when a lower-level system starts, specify the following. In this case, the OS does not perform address resolution.

RESOLVE_BY_SYSCNS=YES

If this specification is omitted, addresses are resolved by the OS. In this case, the JP1/Software Distribution system configuration is not used to perform address resolution.

(21) Timing for sending the result file to the server

To send a result file to a higher-level system when the result file is received from a lower-level system, specify the following. Specify this when you want to check the job execution results immediately.

SEND_RESULT=IMMEDIATE

If this specification is omitted or transmission based on this specification fails, transmission is performed regularly at the interval specified in WatchTimeofStatus of the settings file.

(22) 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:

(23) 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.

(24) Reporting of inventory information to a higher-level system during automatic registration of system configuration

To also report the system information and software information when automatically registering the system configuration, specify the following:

INVENTORY_UPLOAD=YES

If this specification is omitted, NO is assumed and neither the system information nor the software information is reported. Note that this specification is ignored if REALTIME_INVENTORY is set to YES.

When you specify YES here, you must also specify the following:

[Contents][Back][Next]

[Trademarks]

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