JP1/IT Desktop Management 2 - Agent (For UNIX
Systems)
3021-3-B62(E)
Notices
■ Relevant program products
JP1/IT Desktop Management 2 - Additional License for Linux
P-8142-7GBL JP1/IT Desktop Management 2 - Agent 11-00 (for Linux (x64)) JP1/IT Desktop Management 2 - Additional License for UNIX
P-1M42-7FBL JP1/IT Desktop Management 2 - Agent 11-00 (for AIX) P-9D42-7FBL JP1/IT Desktop Management 2 - Agent 11-00 (for Solaris) P-1J42-7FBL JP1/IT Desktop Management 2 - Agent 11-00 (for HP-UX (IPF))
This manual can be used for the products other than the products shown above. For details, see the Release Notes.
■ Trademarks
HITACHI, JP1 are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and other countries.
IBM, AIX are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Itanium is a trademark of Intel Corporation in the United States and other countries.
Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Microsoft Office is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United States and other countries. Symantec is a trademark or a registered trademark of Symantec Corporation or its affiliates in the U.S. and other countries.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows Vista is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Other company and product names mentioned in this document may be the trademarks of their respective owners. The following program product contains some parts whose copyrights are reserved by Oracle Corporation, its subsidiaries, or affiliates: P-9D42-7FBL
The following program product contains some parts whose copyrights are reserved by UNIX System Laboratories, Inc.: P-9D42-7FBL
■ Restrictions
Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license
agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty.
Material contained in this document may describe Hitachi products not available or features not available in your country.
No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.
■ Issued
Jan. 2016: 3021-3-B62(E)
■ Copyright
Preface
This manual describes the functions and operations of the following program products:
• JP1/IT Desktop Management 2 - Additional License for Linux • JP1/IT Desktop Management 2 - Additional License for UNIX
■ Intended readers
This manual is intended for system administrators who are familiar with UNIX operations, and who are responsible for managing and maintaining the software deployed across a network, using the JP1/IT Desktop Management 2 suite of program products.
■ Organization of this manual
This manual is organized into the following parts and appendixes. This manual is for all operating systems. Any differences between operating systems concerning the operation of this program are mentioned at the appropriate place in the manual.
PART 1. Description
This part outlines the specific roles of the program products configured in a JP1/IT Desktop Management 2 system, and describes the features of JP1/IT Desktop Management 2 - Agent.
PART 2. Introduction and Operation
This part describes the setup required at system installation, and the settings required for related program products.
PART 3. Operations
This part explains the syntax of commands. PART 4. Troubleshooting and Messages
This part describes what to do if a problem occurs during program operation. The reason for message output and the recommended action are given for all messages output by JP1/IT Desktop Management 2 - Agent.
Contents
Notices 2 Preface 4
Part 1: Description
1
Overview 10
1.1 Overview of JP1/IT Desktop Management 2 11
1.1.1 Features of JP1/IT Desktop Management 2 11
1.1.2 Types of systems comprising the JP1/IT Desktop Management 2 system 12 1.2 Configuration of a JP1/IT Desktop Management 2 system 13
1.2.1 Network configuration 13
1.2.2 Software configuration 14
1.3 Functions and operating environment of JP1/IT Desktop Management 2 - Agent 16 1.3.1 Organization of JP1/IT Desktop Management 2 - Agent functions 16
1.3.2 Files used by JP1/IT Desktop Management 2 - Agent 16 1.3.3 Conditions for using JP1/IT Desktop Management 2 - Agent 17
2
Software Distribution 19
2.1 Software distribution overview 20
2.1.1 Distribution with UAP startup before and after package installation 20 2.1.2 Distribution specifying the installation timing 20
2.1.3 Distribution specifying the installation date and time 21
2.1.4 Distributing through the selection of the package by the distribution-destination system user 21 2.1.5 Distribution with recovery specified during installation failure 21
2.1.6 Package overwrite installation 21
2.1.7 Distribution with OS restart in distribution-destination systems after installation 22 2.1.8 Preventing package distribution by checking versions 22
2.2 Software registration (packaging) 23 2.2.1 Software classification 23
2.2.2 Packaging procedure 24
2.2.3 Creating the files to be specified during packaging 32
2.2.4 Notes on packaging 44
2.3 Package distribution 45
2.3.1 Checking whether a distribution job exists 45 2.3.2 Notes on package distribution 46
2.4 Package installation 48
2.4.2 Selecting the package to install (Send package, allow client to choose job) 49 2.4.3 Recovery when installation fails 50
2.4.4 Checking the installation result 50 2.4.5 Reporting the installation results 51
2.4.6 File attributes when installing the package 51 2.4.7 Note on package installation 52
2.5 OS patch distribution 53
2.5.1 Formats of distributable OS patches 53 2.5.2 Procedure for distributing an OS patch 53 2.5.3 Notes on configuring the packager 54 2.5.4 Notes on configuring the managing server 55
2.5.5 Required settings in distribution-destination systems and required checking at installation 55
3
File Collection 57
3.1 Overview of file collection 58
3.1.1 Collection by specifying collection timing 58
3.1.2 Collection by starting UAP before or after file collection 58 3.2 Creating a UAP that executes during collection 59
3.3 Executing a file collection job 61
3.4 Note on file collection 62
4
Management of the Distribution-Destination System by the Managing
Server 63
4.1 Overview of distribution-destination management 64
4.2 System configuration management 65
4.2.1 Deleting a client system from the system configuration information 65
4.3 Inventory management 66
4.3.1 System information management 66
4.3.2 Reporting of inventory information from the distribution-destination system 67 4.4 Grouping distribution-destinations 71
4.4.1 ID group 71
4.4.2 ID group definition (client services) 72
4.5 Reporting information to the upper-level managing server 75 4.5.1 Reporting distribution/collection results (client services) 75 4.5.2 Reporting user resource status 75
4.6 Using a related software product to manage the operation status 78 4.6.1 Using JP1/IM - Manager to manage the operation status 78
Part 2: Introduction and Operation
5
Installation Tasks 79
5.2 Estimating of the disk space and memory requirements 81
5.2.1 Disk space requirements for the distribution-destination system 81 5.2.2 Disk space requirements for the packager 84
5.2.3 Memory requirement 85
5.2.4 Changing the work directory 85
5.3 Setting the network environment 87
5.3.1 Setting the port numbers 87
5.3.2 Setting the host name 88
5.3.3 Defining the network interface for JP1/IT Desktop Management 2 89 5.3.4 Settings when using firewalls 91
5.3.5 Examples of operating environment setup 93
5.4 Creating settings files 97
5.4.1 General rules for the settings files 97
5.4.2 Syntax of the end workstation settings file 100 5.4.3 Syntax of the client workstation settings file 104
5.5 Creating the settings file (environment settings file) for the generator tools 107 5.5.1 Environment settings file name 107
5.5.2 Syntax of the environment settings file 107
5.6 Setting the language for messages 110
5.6.1 Files that specify LANG and TZ 110 5.6.2 Example of changing the language 111
5.7 Configuring the operating-environment settings file 112 5.7.1 File name for the operating-environment settings file 112 5.7.2 Items set in the operating-environment settings file 112
5.8 Setting the system files 119
5.8.1 Setting HP-UX system files 119 5.8.2 Setting Solaris system files 119 5.8.3 Setting AIX system files 120 5.8.4 Setting Linux system files 121
5.9 Creating the backup directory 122
5.9.1 How to create the backup directory 122 5.9.2 Notes on creating the backup directory 122
6
Operating the System 123
6.1 Managing the temporary collection storehouse 124 6.1.1 Initializing the temporary collection storehouse 124
6.1.2 Forcibly deleting resources from the temporary collection storehouse 124 6.1.3 Allocating the temporary collection storehouse 124
6.2 Package backup 125
6.2.1 Acquiring backups 125
6.2.2 Managing backups 127
7
JP1 Event Processing Using JP1/IM - Manager 130
7.1 Overview of the operations using JP1/IM - Manager 1317.1.1 Overview of the automated action function 131
7.1.2 Preparations for using the automated action function 132 7.1.3 Notes on using the automated action function 132
7.2 Details of JP1 events that JP1/IT Desktop Management 2 - Agent may send 134 7.2.1 JP1 Events issued by the client services 134
7.2.2 JP1 Events issued by the generator tools 137
Part 3: Operations
8
Command Operations for Client Services and Generator Tools 140
Types of commands 141 Method of command input 143
How to read the command syntax description 144 rdsbkclear 145 rdscfclr 146 rdscm 147 rdsft 153 rdsiddefine 158 rdsidexec 161 rdsinsset 162 rdskillsrv 164 rdslistdel 165 rdslst 166 rdsma 168 rdsrecover 169 rdsrf 171 rdsrsclst 173 rdsstart 175 rdssts 176 rdssys 177 rdsupt 178 rdsusnd 180
Part 4: Troubleshooting and Messages
9
Troubleshooting 182
9.1 Checking failure information by messages 183 9.1.1 Failure information during packaging 183
9.1.2 Failure information during package distribution or file collection 183 9.2 Failure types and troubleshooting 187
9.2.1 Failures in the client services 187
9.2.2 Failures in a program performing user-specific processing 189 9.3 Acquiring failure information 190
rdscltget command 190 rdscltslget command 191 rdsget command 193
10
Messages 195
10.1 Message format 196
10.1.1 Message output format 196
10.1.2 Formats for messages output during package distribution or during file collection 196 10.1.3 Severity of messages that are reported to the managing server 197
10.2 Messages for client services 198
10.3 Messages for generator tools 359
Appendixes 366
A File Structures in JP1/IT Desktop Management 2 - Agent 367 A.1 File structure of the client services 367
A.2 File structure of the generator tools 370
B Status Codes 371
B.1 Status codes for the client services 371
C Port Numbers 375
C.1 Port numbers 375
C.2 Direction in which data passes through the firewall 375
D Processes for Monitoring JP1/IT Desktop Management 2 - Agent 376 D.1 Monitoring processes for systems other than HP-UX 376
D.2 Monitoring processes for HP-UX 377
E Kernel Parameter List 378
E.1 For HP-UX 378
E.2 For Solaris 378
E.3 For AIX 378
E.4 For Linux 378
F Differences with JP1/IT Desktop Management 2 for Windows 379
G Reference Material for This Manual 380
G.1 Related publications 380
G.2 Conventions: Abbreviations for product names 380
G.3 Conventions: Acronyms 382
G.4 How to use this manual 383
G.5 Conventions: Fonts and symbols 383
G.6 Conventions: KB, MB, GB, and TB 384
H Glossary 385
Part 1: Description
1
Overview
When a networked system consists of a great many UNIX and Windows machines, managing the
software resources across the whole system can be onerous and time-consuming. JP1/IT Desktop
Management 2 - Agent and the other programs in JP1/IT Desktop Management 2 are designed to
enable centralized management of all the software resources in a networked system.
This chapter describes the basic functions and configuration of a JP1/IT Desktop Management 2
system that uses the programs in the JP1/IT Desktop Management 2 series.
1.1 Overview of JP1/IT Desktop Management 2
JP1/IT Desktop Management 2 is a group of programs for distributing software over a network. The following describes the main programs and their functions.
• JP1/IT Desktop Management 2 - Manager (Windows only): Software distribution feature • JP1/IT Desktop Management 2 - Agent (Windows only) (relay system): Software relay function
• JP1/IT Desktop Management 2 - Agent (distribution-destination system): Software distribution destination functions
Hereafter, unless it is necessary to differentiate JP1/IT Desktop Management 2 - Manager and JP1/IT Desktop Management 2 separately, they (the three programs listed above) will be generically referred to as JP1/IT Desktop
Management 2.
To distribute software using JP1/IT Desktop Management 2, the applicable programs from those shown above must be installed and set up on all machines used for distribution.
The network in which the JP1/IT Desktop Management 2 programs are installed and which enables distribution management of software is called the JP1/IT Desktop Management 2 system.
1.1.1 Features of JP1/IT Desktop Management 2
A system that uses the JP1/IT Desktop Management 2 programs for managing software distribution has the following features:
• Less work involved in software distribution
Using command-driven operations at a central server, you can distribute software in a single operation to a large number of machines in a distributed environment. Distributed software is installed automatically, so there is no need to set up the destination machines individually. Also, you can centrally manage distribution and installation results on the central server.
• Hierarchical management of software distribution
In a large-scale system, relay machines can be used for software distribution, lessening the load on the network. By using the relay machines as departmental servers, you can distribute software across the whole networked system, or to selected departments only.
• Precise distribution operations
JP1/IT Desktop Management 2 provides a variety of distribution methods, which can be selected according to the system operation. For example, software can be distributed at a specified date and time, or to a specific group of machines.
• Applicable to a wide range of systems or platforms
JP1/IT Desktop Management 2 can be used whatever the size of your system, from a small system comprising a few dozen machines, up to a large-scale network with thousands of machines. The JP1/IT Desktop Management 2 programs also support cross-platform environments with both Windows and UNIX machines.
• Support for inventory control
The JP1/IT Desktop Management 2 system not only distributes software. The managing server in the system can retrieve and manage the inventory information of each machine in a network. The inventory information you can manage includes hardware information, software installation status, and user-specific inventory information.
1.1.2 Types of systems comprising the JP1/IT Desktop Management 2
system
In JP1/IT Desktop Management 2, the machines (UNIX and Windows) that make up the network can be divided by purpose into four types:
Managing server
Distributes software, and manages the distribution process and the installation status at the destination machines. The program JP1/IT Desktop Management 2 - Manager provides this functionality.
Relay system
Used as a relay point when distributing software. JP1/IT Desktop Management 2 - Agent (relay system) provides this functionality.
Distribution-destination system (client)
The target system to which software is distributed. JP1/IT Desktop Management 2 - Agent (distribution-destination system) provides this functionality.
A distribution-destination system that runs the UNIX version of JP1/IT Desktop Management 2 - Agent (distribution-destination system) is an end workstation if it is connected directly to the managing server. If packages are distributed via a relay system, the distribution-destination system is called a client workstation. Note that, in JP1/IT Desktop Management 2 - Agent documentation, the term workstation refers to UNIX workstations only.
Packager
Used for registering software to be distributed on the managing server. JP1/IT Desktop Management 2 - Agent provides this functionality.
1.2 Configuration of a JP1/IT Desktop Management 2 system
This section describes the network configuration and software configuration of a JP1/IT Desktop Management 2 system.
1.2.1 Network configuration
Figure 1-1 shows a network configuration example of a JP1/IT Desktop Management 2 system.
Figure 1‒1: Network configuration example
Note that in the UNIX version of JP1/IT Desktop Management 2 - Agent, the commands that can be used and the environmental settings details differ depending on whether the managing server is connected directly or via a relay system. Therefore, a system that is connected directly to the managing server (including a Windows relay system) is called an end workstation, and a system that is connected via a relay system is called a client workstation.
For details about network configurations where UNIX and Windows coexist, see (3) Network configurations where
Windows systems coexist.
(1) Network configuration under JP1/IT Desktop Management 2 - Manager
as a managing server
JP1/IT Desktop Management 2 series of programs operates in a WAN or LAN environment. TCP/IP is used over a LAN. JP1/IT Desktop Management 2 also supports firewalls.
One or more relay systems (JP1/IT Desktop Management 2 - Agent) can be configured between the managing server (JP1/IT Desktop Management 2 Manager) and the distributiondestination systems (JP1/IT Desktop Management 2 -Agent). It is also possible to connect a managing server directly to a distribution-destination system (end workstation) without using any relay systems. The managing server includes a Windows relay system for management.
(2) Network configuration with multiple LAN connections
When the system consists of multiple local area network (LAN) connections, you can select the LAN used by each host in JP1. This function is called multiple LAN connections.
• When the network is separated into segments
You can set the managing server to use the right LAN for each distribution-destination system, without changing the LAN settings.
In the /etc/hosts file at the managing server, you must preset all the LAN settings to be used.
• When the managing server uses multiple networks
Using JP1/IT Desktop Management 2 on the distribution-destination systems, you can switch to the preset LAN connection without changing the LAN settings.
In the /etc/hosts file at the distribution-destination system, you must preset all the LAN settings to be used. In the network interface definition file, you must define the LAN settings for the JP1/IT Desktop Management 2 system. For details on settings, see 5.3.3 Defining the network interface for JP1/IT Desktop Management 2.
(3) Network configurations where Windows systems coexist
Figure 1-2 shows system configurations in which Windows systems coexist.
Figure 1‒2: Network configuration where Windows systems coexist
To perform packaging for JP1/IT Desktop Management 2 - Manager in an environment where a UNIX and Windows JP1/IT Desktop Management 2 - Agent coexist, note the following:
Cabinet ID is assigned to both the cabinet name and cabinet ID, for the cabinet created in the Windows systems. To set a name for the UNIX cabinet displayed on the Windows screen, register the cabinet in the Windows JP1/IT Desktop Management 2 - Manager, and then set a name at that time.
1.2.2 Software configuration
The following describes the software that makes up a JP1/IT Desktop Management 2 system, and the prerequisite programs for JP1/IT Desktop Management 2 - Agent.
(1) Software used in a JP1/IT Desktop Management 2 system
The software used in a JP1/IT Desktop Management 2 system is described below.
(a) Software for the managing server
The following software runs on the managing server: JP1/IT Desktop Management 2 - Manager
Provides managing server functions.
(b) Software for the relay systems
The following software runs on the relay systems:
JP1/IT Desktop Management 2 - Agent (Windows version)
This program provides the functions of relay systems, distribution-destination systems, and packagers.
(c) Software for the distribution-destination systems
The following software runs on the distribution-destination systems: JP1/IT Desktop Management 2 - Agent (Windows version, UNIX version)
This program provides distribution-destination system functions and packager functions.
(2) Software relating to JP1/IT Desktop Management 2 - Agent functions
The following software is required to use JP1/IT Desktop Management 2 - Agent. JP1/IM - Manager
This JP1 program enables events to be monitored across the network, and actions to be executed automatically in response to events. In JP1/IT Desktop Management 2 - Agent, events that occur can be automatically reported to JP1/IM - Manager such that actions are executed automatically in response to events.
For details on linking JP1/IT Desktop Management 2 - Agent with JP1/IM - Manager, see 7. JP1 Event Processing
1.3 Functions and operating environment of JP1/IT Desktop Management
2 - Agent
Along with the basic services that form the core processing, JP1/IT Desktop Management 2 - Manager and JP1/IT Desktop Management 2 - Agent provide additional services.
This section describes how functions and files are organized in JP1/IT Desktop Management 2 - Agent, and the conditions for using the program.
1.3.1 Organization of JP1/IT Desktop Management 2 - Agent functions
The functions provided by JP1/IT Desktop Management 2 - Agent can be broadly classified as client services and
generator tools. These two types of functions differ in various ways, including their file structure and user interface. It
is important to understand the differences in order to use the functions properly. The features of the two types of functions are outlined below
Client services
Client services provide the functionality for operation as a destination system or packager (system at which packages are registered). These services normally launch automatically at machine startup and are available as resident services.
Generator tools
Generator tools are additional capabilities of JP1/IT Desktop Management 2 - Agent. The generator tools launch automatically when distributing packages for which the installation date and time are specified.
For details on the functionality of the generator tools, see 2.4 Package installation.
The generator tools only cover the installation related services of the distribution-destination system of the client services. For details on the role of the generator tools, see 2.4 Package installation.
1.3.2 Files used by JP1/IT Desktop Management 2 - Agent
This section describes the files that must be created or modified for using JP1/IT Desktop Management 2 - Agent. For other information see the following:
File (directory) structure
See Appendix A. File Structures in JP1/IT Desktop Management 2 - Agent. Disk space requirement for files
See 5.2 Estimating of the disk space and memory requirements in PART 2.
(1) Files used by the client services
Table 1-1 lists the files used by the client services of JP1/IT Desktop Management 2 - Agent.
Table 1‒1: Files used by JP1/IT Desktop Management 2 - Agent (client services)
File type Name Purpose
Files used at packaging
File type Name Purpose Files used at
packaging
User resource path file Specifies the directory from which to package a user resource from the hard disk. Special file definition file Specifies the device special files to be used for packaging.
Directories for storing packages
Temporary collection storehouse
An area on a relay system used to temporarily store resource files collected from lower-level systems if a line error occurs between the managing server and the relay system.
Files for reporting information to an upper-level system
User resource status file Used to report user information, such as the status of packages installed locally (without using JP1/IT Desktop Management 2 - Manager), to the managing server. Settings file Defines the operating environment for the client services.
File for setting the environment Sets an operating environment in detail for distribution-destination system. ID group definition file# Stores ID group information for organizing distribution-destination systems as
groups.
Network interface definition file Defines the network interfaces used by JP1/IT Desktop Management 2 in order of priority.
Log files Log file Contains the processing log for the client services. File for file system error
information
Stores error information. #
Used in client workstation
(2) Files used by the generator tools
Table 1-2 lists the files used by the generator tools of JP1/IT Desktop Management 2 - Agent.
Table 1‒2: Files used by JP1/IT Desktop Management 2 - Agent (generator tools)
Name Purpose
Directory for installation-scheduled packages
Directory for temporarily storing packages waiting to be installed at a scheduled date/time Environment settings file Sets the operating environment for the generator tools.
Log file Contains the processing log for the generator tools. Error log file Contains the error log for the generator tools.
1.3.3 Conditions for using JP1/IT Desktop Management 2 - Agent
When using JP1/IT Desktop Management 2 - Agent, note the following:
• Language settings of the machine
• In a system environment where machines that use different Japanese encodings coexist, you might not be able
to use the Japanese language. You must use the same Japanese encoding system for all machines.
• Cautions when using on HP-UX
• When using JP1/IT Desktop Management 2 - Agent under HP-UX, avoid using large user IDs and large files. • Free space required for startup
• At least 5 megabytes of hard disk space is required to start JP1/IT Desktop Management 2 - Agent. • Changing system time
You can change the system time when stopping the JP1/IT Desktop Management 2 - Agent system. Note that changing the system time might cause the following problems.
• A job with the date and time specified is executed at an unexpected time.
• When the system time is rolled back, a job with the date and time specified is executed twice. • It becomes difficult to analyze the causes of failure because the log output times will deviate.
If a job is created after the system time is rolled back, a registered job might be overwritten. Wait for the time of the roll back to pass before creating a job.
2
Software Distribution
Software distribution is functionality of a JP1/IT Desktop Management 2 system, and performs batch
distribution to the systems on a network. This chapter discusses the four stages of software
distribution: software registration (packaging), package management, package distribution, and
package installation.
2.1 Software distribution overview
This section describes the functions of the entire JP1/IT Desktop Management 2 system and the functions which JP1/IT Desktop Management 2 - Agent is responsible for.
2.1.1 Distribution with UAP startup before and after package installation
You can start a program that performs user-specific processes before or after a package is installed, by specifying the startup when you register software or specify distribution. The program is started by a user with superuser permissions.
(1) UAP startup process created in using the client services
You can specify the following UAP startup processes when using the client services. For details on how to create UAPs, see 2.2.3(4) Creating the UAPs to be started during installation (client services).
Type of process Description Example of UAPs registered
External program processing for installation
Starts a UAP before or after installation of another company's software, user programs and user data, or an OS patch. This type of processing is divided into the following two major categories:
• External program processing before installation
Processes executed before installation.
• External program processing after installation
Processes executed after installation.
For another company's software or an OS patch:
• Startup of installed software • Startup of related software
• Stop of the same software as that to be installed
For user programs and user data:
• Registration of distributed Gaiji characters • Message output after installation
• Compiling the distributed source program and
creating the object program External program
processing after market software installation
Starts the UAP after completion of Hitachi program product installation (setup).
• Startup of the installed Hitachi program product • Startup of related Hitachi program products • Stop of installing Hitachi program products • Deletion of the work file
2.1.2 Distribution specifying the installation timing
Unless otherwise specified, packages distributed to the distribution-destination system are immediately installed into the destination system. However, the installation fails if that software is in use or running in the distribution-destination system. To prevent such a problem, you can set an installation timing.
Specify the installation timing during the registration or distribution of software. The following installation timings can be specified.
• During system startup • During system operation • During system stop
When installation during system startup or during system stop is selected, the distributed package is stored in the hard disk of the distribution-destination system until installation.
For details about the precautions for the distribution-destination system when the installation timing is specified, see
2.1.3 Distribution specifying the installation date and time
When an installation date and time is specified for a package, the package that reaches the installation date and time will be automatically installed at the distribution-destination system.
You can specify an installation date and time for both Windows and UNIX distribution-destination systems. You can only specify the installation data and time for user data, user programs and OS patch.
2.1.4 Distributing through the selection of the package by the
distribution-destination system user
Normally, when a package is distributed, the installation process is started regardless of the operating condition of the distribution-destination system. This can cause a problem in the system operation. To avoid this, you can allow the users at the distribution-destination systems to select whether or not to install the packages. This is called client-user selected
installation. When this feature is used, even if the managing server distributes a combination of UNIX and Windows
packages, the user can select and install the package applicable to the distribution-destination system.
You can specify this method only when distributing packages from JP1/IT Desktop Management 2 - Manager. For details on the procedure for client-user selected installation, see 2.4.2 Selecting the package to install (Send package, allow
client to choose job).
2.1.5 Distribution with recovery specified during installation failure
If installation of the distributed package fails, it is possible to perform recovery to the old version, by specifying the recovery in the packaging-information file during packaging.
When a distribution job which specifies recovery is executed, the distribution-destination system acquires a backup of the old version, and then begins installation of the package. If the package is not installed, the distribution-destination system uses the backup of the old version to perform recovery. The execution results of the recovery are reported to the managing server as a recovery status.
For details on specifying recovery during packaging, see 2.2.3(1) Creating the packaging-information file. For recovery operation during installation, see 2.4.3 Recovery when installation fails.
2.1.6 Package overwrite installation
Normally, if a package that has the same name as the package you want to distribute has already been installed in a destination system, the package is not distributed to the destination system. However, if overwrite installation is set during distribution, the new package will be forcibly distributed, overwriting the package that already exists in the distribution-destination system.
2.1.7 Distribution with OS restart in distribution-destination systems after
installation
When you create a distribution job, you can specify whether to restart the operating system in the distribution-destination systems after the desired package is installed. If you do not specify the restart of the operating system in the distribution-destination systems at the creation of the job, the settings specified at packaging take effect.
2.1.8 Preventing package distribution by checking versions
Before distributing an update version of a program product, you can check whether the base version that of the update version has been installed in the distribution-destination. If it has not, a message is output. This prevents distribution of unnecessary packages.
(1) Specifying the base version of the update version
When distributing to a UNIX machine, specify the version as attribute information during packaging. This specification can be altered during creation of the distribution job.
(2) Timing for checking versions
The following shows when the version check is performed. For UNIX distribution-destination systems
2.2 Software registration (packaging)
In order to distribute a software resource, it must be registered on the managing server. This is called packaging. Make sure that the software does not exceed 2 gigabytes before and after registration. The name of a file or directory registered as a resource must not contain spaces, character strings enclosed in (), [], or {}, or the following special 1-byte characters.
$, !, *, ?, ;, &, ", ', `, ^, \, |, <, >
You register software resources from JP1/IT Desktop Management 2 - Agent. The system at which the user registers a package is called a packager. At the managing server, the administrator can set a password to check whether any user attempting to register a package is authorized to do so.
Packages can be compressed at packaging time, which reduces the amount of the following data:
• Amount of data during packaging
• Disk space at the package storehouse on the distribution-destination system
In addition, compressed packages are not expanded until installation on a distribution-destination system, thereby reducing the amount of data at distribution.
2.2.1 Software classification
In a JP1/IT Desktop Management 2 - Agent system running under UNIX, software that can be registered is classified into four types, as follows. This classification is called the package type.
Hitachi program products
Hitachi software products. Some of these are not permitted to be distributed. For Hitachi program products that can be distributed, see the relevant documentation or Release Notes.
Program products that can be registered include JP1/IT Desktop Management 2 - Agent and other programs in the JP1/IT Desktop Management 2 series. That is, you can upgrade the JP1/IT Desktop Management 2 system itself, using the program functions.
Another company's software
Commercially available software from companies other than Hitachi. In principle, another company's software that can be distributed is a multi-license pack product. Distribution of such a product might not be permitted with a general license. Before distributing another company's software product, obtain approval from the vendor.
User data and user programs
Files can be packaged singly or in sets. You can also package files located in different directories as a single package. Packages containing user data or user programs that can be distributed to both UNIX machines and Windows machines are called shared packages.
OS patches
OS patches correct problems in operating systems. JP1/IT Desktop Management 2 can package the OS patches that have not yet been applied to the destinations systems. You distribute the OS patches to the distribution-destination systems to centrally correct the problems in the operating systems. For details about the formats of OS patches that can be distributed and the procedure for distributing an OS patch, see 2.5 OS patch distribution.
2.2.2 Packaging procedure
You can package a resource by a command. How to register the software by using a command
Create and register a file (packaging-information file) which specifies attribute information (package attribute) such as the name of the software to be registered, and the installation method during distribution.
To register Hitachi program products or register user programs and user data to be distributed to machines whose OS is the same as the OS of the registration source, use the rdsft command. To register another company's software, register OS patches, or register user programs and user data to be distributed to machines whose OS differs from the OS of the registration source, use the rdscm command. The rdscm command can also register user programs and user data to be distributed to machines whose OS is the same as the OS of the registration source.
Hitachi program products and another company's software can only be distributed to machines whose OS is the same as the OS of the registration source.
This section explains procedures for registering software using commands.
(1) Registering Hitachi program products
This subsection describes how to register Hitachi program products.
(a) Registration method
Use the rdsft command to register Hitachi program products.
To specify detailed attributes, create the packaging-information file before you register resources and specify that file name in the command option. For the method of creating the packaging-information file, see 2.2.3(1) Creating the
packaging-information file. For some items, you can set default values in the settings files of the client services.
Table 2-1 lists the rdsft command options to be specified and the items to be specified in the packaging-information file when you register program products. If the same item is specified using more than one method, the order precedence is the rdsft command, the packaging-information file, and then the settings file.
Table 2‒1: Items to be specified when a Hitachi program product is registered
Item Specification method Default
rdsft command Packaging-information file Settings file -k password Y -- -- --#1 -C special-file-name #2 Y -- -- ---s or -S registered-program-product-model #2 Y -- -- --cabinet-ID-1 #2 Y Y -- ---m managing-host-name Y -- -- --#3 -Q Y -- -- --#4
host-name-on-higher-system Y Y -- Value in the settings file
packaging-information-file-name Y -- --
--Item Specification method Default rdsft command Packaging-information file Settings file APafterGeneration -- Y -- --APWatchTimer -- Y -- 300 seconds InstallTiming -- Y -- EXECUTE Compress -- Y Y NO LifeofResource -- Y Y 1 day Recover -- Y -- NO BackupDataKeep -- Y -- 0 days Legend: Y: Specifiable.
--: Not specifiable or inapplicable. #1
Requires the password. #2
Mandatory. #3
For -m managing-host-name, specify the host name of the relay system that is directly connected to the managing server if program products are registered via at least two relay systems. This item does not need to be specified if program products are registered from the end workstation, the UNIX machine connected to the relay system that is directly connected to the managing server.
#4
Waits for the response from the user. #5
Mandatory if -s is specified in the rdsft command.
If you want to register a Hitachi program product by using a special file that is not a system standard special file, you must define the special file in the special file definition file. For details on how to create the special file definition file, see 2.2.3(3) Setting the special file definition file.
(b) Note during registration
After execution of the register command (rdsft command), you cannot cancel the packaging. To make sure that the software is registered, execute the rdslst command after creation of the packaging-information file, and check the specified Hitachi program product.
The rdslst command, also allows you to confirm the Hitachi program products stored on a storage medium. For example, a CD-ROM might contain a Hitachi program product that is not licensed. Before registering a program product, use the rdslst command to check the stored Hitachi program products. Execute the rdslst command with the medium unmounted. Execute the packaging with the CD-ROM also unmounted.
(2) Registering another company's software
This subsection describes the formats of another company's software that can be distributed and the method for registering that software.
(a) Formats of another company's software that can be distributed
Table 2-2 describes the formats of another company's software that can be distributed by using JP1/IT Desktop Management 2.
Table 2‒2: Formats of another company's software that can be distributed
OS Software format Software format example
HP-UX File formats that can be specified in the -s option of the swinstall command
depot Solaris File formats that can be specified in the -d option of the pkgadd
command
Solaris package format AIX File formats that can be specified in the -d option of the
geninstall command
bff Linux File format that can be specified in the rpm command rpm
If the OS command allows, you can specify a directory.
The following software of another company cannot be distributed:
• Software that must be installed in the single-user mode, which is one of the OS operation modes • Software that requires the OS to be restarted during installation
(b) Registration method
To register another company's software, use the rdscm command with the -ISVSOFT option specified. Depending on the situation, you might need to perform the file creation tasks described below before registration:
Creating a packaging-information file
You can use command options to specify major attributes such as package ID and cabinet ID. However, if you want to specify more detailed attributes, you need to create a packaging-information file. For details on how to do this, see 2.2.3(1) Creating the packaging-information file.
Creating a response file
If you want to distribute another company's software that requires user responses during installation, you must specify the appropriate response file during packaging. A file that describes user responses is called a response file. You can specify a response file in HP-UX and Solaris only. The following shows the command for creating the response file:
HP-UX: swask -c Solaris: pkgask -r
For details on the response file, see the documentation for the OS. Creating an installation management file
To distribute the Solaris version of another company's software, you need to specify an installation management file during packaging. The installation management file describes information needed during installation. For example, you might be able to indicate forced distribution by using the file.
For details on how to create the installation management file, see the documentation for the OS.
Table 2-3 lists the items that you can specify by using command options or a packaging-information file when registering another company's software. For some of the items, the default values can be specified using the settings file for the client services. If the same item is specified using more than one method, the order of precedence is command, package-information file, and settings file.
Table 2‒3: Items to be specified when another company's software is registered
Item Specification method Default
rdscm command Packaging-information file Settings file -ISVSOFT#1 Y -- -- ---k password Y -- -- --#2 -d user-resource-path#1 Y -- -- --cabinet-ID#1 Y Y --
--package-ID Y Y -- Automatic generation
program-name Y Y -- Space character#3
version Y Y -- 000000#3
generation Y Y -- 0000
host-name-on-higher-system Y Y Y Value in the settings file
-m managing-host-name Y -- -- --#4 -Q Y -- -- --#5 packaging-information-file-name Y -- -- ---N service-name Y -- -- ---REBOOT Y -- -- ---ISVRES response-file-name#6 Y -- -- ---ISVADM installation-management-file-name#7
Y -- -- Path defined by the pkgadd
command
UserName -- Y -- Space character
Compress -- Y Y Value in the settings file
APbeforeGeneration -- Y --
--APafterGeneration -- Y --
--APWatchTimer -- Y -- 300 seconds
LifeofResource -- Y Y Value in the settings file
InstallTiming -- Y -- EXECUTE
Recover#8 -- Y -- NO
Legend:
Y: Specifiable.
--: Not specifiable or inapplicable. #1
Mandatory. #2
Requires a password. #3
#4
Specify the host name of the relay system that is directly connected to the managing server if program products are to be registered via at least two relay systems. This item does not need to be specified if program products are registered from the end workstation, the UNIX machine connected to the relay system that is directly connected to the managing server.
#5
Waits for a response from the user. #6
This item can be specified for only the HP-UX or Solaris version of another company's software. #7
This item can be specified for only the Solaris version of another company's software. #8
This item can be specified for only the HP-UX version of another company's software.
(c) Automatic generation of package IDs
When you register another company's software without specifying the package ID, an OS command that acquires software information is executed to generate the package ID automatically. If you also omit specifying the program name and version, the command also automatically generates them.
The OS command used to acquire software information must be stored in a specific directory. Table 2-4 shows the command and the appropriate directory for each OS.
Table 2‒4: OS command for acquiring software information and its directory
OS Command Directory for storing the command
HP-UX swlist /usr/sbin
Solaris pkginfo /bin
AIX geninstall /usr/sbin
Linux rpm /bin
The package ID, program name, and the version are automatically generated from the software short name, software long name, and version information acquired by the OS command. Automatic generation uses the following rules to convert the acquired information:
Package ID
• The string WUA- is prefixed.
• Periods (.) and underscores (_) are converted to hyphens (-).
• Lower-case letters are converted to the corresponding upper-case letters.
• If the package ID has more than 44 characters, it is truncated following the 42nd character and two hyphens (--)
are appended. Program name
• Periods (.) and underscores (_) are converted to hyphens (-).
• Lower-case letters are converted to the corresponding upper-case letters.
• If the program name has more than 50 characters, it is truncated following the 48th character and two hyphens
(--) are appended. Version
• If the version has fewer than 7 characters, zeros (0) are appended to make the length 7 characters. • If the version has more than 7 characters, it is truncated following the 7th character.
(3) Registering the user data and user programs
(a) Registration method
Use the rdsft command to register user data and user programs. Use the rdscm command to register shared packages. Before registration, create the following files as required.
Creating the packaging-information file
options. To specify detailed attributes, create a packaging-information file. For details on how to create this file, see
2.2.3(1) Creating the packaging-information file.
Creating the user resource path file
The directories and files for software where user data and user programs are to be registered are called the user
resource paths. To register all software in different directories as a single unit of software, specify the user resource
paths in a user resource path file. For details on how to create the user resource path file, see 2.2.3(2) Creating the
user resource path file.
Table 2-5 lists the command options to be specified and the items to be specified in the packaging-information file when you register user data and user programs. For some items, you can set default values in the settings files of the client services. If the same item is specified using more than one method, the order precedence is the command, the packaging-information file, and then the settings file.
Table 2‒5: Items to be specified when registering user data and user programs
Item Specification method Inheritance of
specified items when packages are distributed to Windows clients Default rdsft or rdscm command Packagin g-informatio n file Settings file
-k password S -- -- -- A password is requested.
-d resource-path or -D user-resource-path-file-name S -- -- -- A directory under /NETMRDS/UPUPL/hd #1 cabinet-ID#2 S S -- I --package-ID#2 S S -- I
--program-name S S -- I Space character
-m managing-host-name S -- -- -- --#3
-L installation-mode#4 S -- -- I B
-Q S -- -- -- A response from the user is
waited.
host-name-on-higher-system S S -- -- Value in the settings file packaging-information-file-name S -- -- -- /NETMRDS/UPUPL/
AC000000#5
version S S -- I 000000
Item Specification method Inheritance of specified items when packages are distributed to Windows clients Default rdsft or rdscm command Packagin g-informatio n file Settings file generation-number S S -- I 0000
owner-name -- S -- NI Space character
Generator -- S -- NI STANDARD
APbeforeGeneration -- S -- NI
--APafterGeneration -- S -- NI
--APWatchTimer -- S -- NI 300 seconds
Comments -- S -- NI Space character
InstallDirectory -- S -- NI / (root directory)
OwnerofInstallDirectory -- S -- NI User number 0
GroupofInstallDirectory -- S -- NI Cabinet number 3
ModeofInstallDirectory -- S -- NI 755 InstallTiming -- S -- I#6 EXECUTE Compress -- S S NI NO LifeofResource -- S S I 1 day Recover -- S -- NI NO BackupDataKeep -- S -- NI 0 days
UAPBackupList -- S -- NI File with the name of the
distributed package#7 Legend:
S: Specifiable.
--: Not specifiable, inapplicable, or a value used only at registration. I: Inherited by the Windows machine.
NI: Not inherited by the Windows machine. #1
For HP-UX, a directory under /var/opt/NETMDMW/UPUPL/hd #2
Mandatory. #3
To register user data or user programs via two or more relay systems, specify the host name of the relay system that is directly connected to the managing server. This specification is unnecessary when registering user data or user programs from the end workstation, the UNIX machine connected to the relay system that is directly connected to the managing server.
#4
#5
Assumed if you do not specify the packaging-information file name, user resource path, and user resource path file specifications are omitted. For HP-UX, it will be /var/opt/NETMDMW/UPUPL/AC000000.
#6
In the distribution-destination system of Windows, installation is not executed at system stop. #7
The backups of the file and the directory to be overwritten are acquired.
(b) Shared package attributes that can be inherited by the distribution-destination
system
When the distribution-destination system inherits shared packages, it can inherit the following file attributes.
• File name
• File update time and date
• Name of the user who owns the file • Cabinet ID which owns the file
• Access privilege of the user who owns the file (read, write, and execute) • Access privilege of the cabinet who owns the file (read, write, and execute) • Access privilege of the other users and cabinets (read, write, and execute)
(c) Directory configuration of the packager and the distribution-destination system
Figure 2‒1: Directory configuration of the packager and the distribution-destination system
2.2.3 Creating the files to be specified during packaging
(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
attribute-nameTabvalueEnter 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.
• You can specify a space character instead of a tab character.
• To include a space character in a set value, enclose the set value between double quotation marks ("). • If you specify # in the first column, that line is treated as a comment.
• The maximum length of a line in the packaging-information file is 256 bytes including the code for the pressed Enter key.
• If you specify more than one attribute with the same name, the set value that is specified last is validated and the
preceding set values are ignored.
(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-name-on-higher-system] [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] [Recover {YES|NO}] [BackupDataKeep backup-file-storage-period] For registering another company's software and OS patches
Group cabinet-ID [ResourceName package-ID] [ProgramName program-name] [Version version] [Generation generation-number] [HostName host-name-on-higher-system] [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-name-on-higher-system] [Compress {NO|COMPRESS|PACK|COMMON}] [Generator {STANDARD|NETM_DM_GF}] [APbeforeGeneration external-program-processing-before-installation] [APafterGeneration external-program-processing-after-installation] [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 might 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 space characters 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-.
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 space character 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 space character 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 space character 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 space character is assumed.
HostName host-name-on-higher-system ~ <uppercase alphabetic characters, numerics, hyphens, underscores, or periods> ((1 to 20 characters))
Specify the host name on higher system. 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 name of the relay system.
If you do not specify a host name on higher level in the option of the rdsft or rdscm command, the specification in the packaging-information file is validated. The host name on higher system specified in the rdsft or rdscm command takes precedence over the specification in the packaging-information file. Compress ~ {NO|COMPRESS|PACK|COMMON}
• 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 JP1/IT Desktop Management 2 - Agent
• NETM_DM_GF
Generator provided by the generator tools of JP1/IT Desktop Management 2 - Agent
APbeforeGeneration external-program-processing-before-installation ~ ((1 to 60 characters))
Use the absolute path to specify the external program processing before installation which is started before the standard generator executes installation. If you also specify APafterGeneration (external program processing after installation), 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 processing before installation is ignored even if it is specified.
By creating the program of the external program processing before installation 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 processing before installation:
• Up to 18 character strings (arguments) can be specified. • Consecutive space characters 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 space character 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 installation or
external-program-processing-after-market-software-installation ~ ((1 to 64 characters))
Use the absolute path to specify the external program processing after installation or the external program processing after market software installation which is started after a package is installed.
This specification is valid when distributing to the workstation. The installation is ignored when distributed to a PC. When you specify NETM_DM_GF is specified for Generator, specify in less than or equal to 40 characters.
