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

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

rdscm

The rdscm command registers a shared package.

Description

This command specifies that a user program and user data on a hard disk are to be registered as a shared package. You can also use this command to register another company's software, register OS patches, and register user programs and user data to be distributed to machines that run on the same OS as the OS of the local machine.

Format

rdscm[-ISVSOFT]
[-kpassword]
[-Pinstallation-script-file-name]
[{-duser-resource-path|-Duser-resource-path-file-name}]
[-gcabinet-ID]
[-rpackage-ID]
[-pprogram-name]
[-vversion]
[-Vprerequisite-version]
[-Ggeneration-number]
[-hhost-file-name or host-name]
[-mmanaging-host-name]
[-Linstallation-mode]
[-Q]
[-tinstallation-date/time]
[packaging-information-file-name]
[-Nservice-name]
[-OSPATCH]
[-REBOOT]
[-ISVRESresponse-file-name]
[-ISVADMinstallation-management-file-name]

Options

-Duser-resource-path-file-name ~ ((1 to 128 characters))
Specify the name of a user resource path file. Specifying this option enables JP1/Software Distribution Client to execute packaging of multiple directories and files in a batch. For information on how to create a user resource path file, see 2.2.4(2) Creating the user resource path file. You must not specify the -D option together with the -d option. Do not specify a path using two consecutive periods (..).
If you omit the -D option, JP1/Software Distribution Client distributes directories or files under /NETMRDS/UPUPL/hd/ or /var/opt/NETMDMW/UPUPL/hd/ (HP-UX). If packaging of an empty directory is executed, only the directory frame is restored on the distribution destination.

-duser-resource-path ~ ((1 to 128 characters))
Specify the absolute or relative path of a directory that stores the resources you want to package.
You must not specify option -d together with option -D. Do not specify a path using two consecutive periods (..).
If you omit the -d option, JP1/Software Distribution Client distributes directories or files under /NETMRDS/UPUPL/hd/ or /var/opt/NETMDMW/UPUPL/hd/ (HP-UX). If you package an empty directory, only the directory frame is restored on the distribution destination.
When you register another company's software or an OS patch, always specify this item using a relative path. Additionally, when you register an OS patch, specify a file name.

-Ggeneration-number ~ <uppercase alphabetic characters or numerics> ((4 digits))
Specify the generation number of the package of resources you want to package. Unless you specify this option and a generation number, the corresponding specification in the packaging-information file is effective. The specification in the -G option has priority over that in the packaging-information file.

-gcabinet-ID ~ <uppercase alphabetic characters or numerics> ((2 characters))
Specify a cabinet ID for packaging. Full up to 256 resources can be packaged in one cabinet. To create a new cabinet and package into it, specify a cabinet ID in this option for the cabinet, then JP1/Software Distribution Client automatically creates the cabinet and can execute packaging.
Register different cabinet IDs with different managing servers. If you register different packages with the same cabinet ID in different managing servers, you may not be able to distribute the packages.
Unless you specify the -g option and a cabinet ID, the cabinet ID specified in the packaging-information file is effective. The specification in the -g option has priority over that in the packaging-information file. If you do not use the packaging-information file, always specify the -g option.

-hhost-file-name or host-name

host-file-name ~ <uppercase alphabetic characters, numerics, hyphens, or underscores> ((1 to 20 characters))
If you want to perform packaging according to the attribute setting specified in a host file, specify the name of the host file.
If you specify option -m, specify the host file of the relay system specified in the -m option.
If you omit the -h option, the corresponding specification in the packaging-information file is effective.
The specification in the -h option has priority over that in the packaging-information file. If you do not specify a host file name in the -h option or the packaging-information file, the value specified in the settings file is effective at the end workstation or the relay system that is directly connected to the managing server. At the client workstation or in a relay system connected to another relay system, either the value in the settings file of the relay system specified in ManagingHost of the local UNIX machine settings file is effective, or the value specified in the settings file of the relay system specified by the -m option is effective.

host-name ~ <uppercase alphabetic characters, numerics, hyphens, underscores, or periods> ((1 to 255 characters))
If you want to perform packaging from a system for which the operating environment is not set, specify the host name of the managing server (UNIX JP1/Software Distribution Manager, UNIX JP1/Software Distribution Client (relay system) or Windows JP1/Software Distribution Manager).

-ISVADMinstallation-management-file-name ~ ((1 to 128 characters))
Specify the absolute path name of the installation management file when you register the Solaris version of another company's software.
When another company's software is distributed, the appropriate standard OS installation command is executed at the distribution-destination systems. At this time, the file specified in the -ISVADM option is used for the -a option of the standard OS installation command pkgadd.
If you omit the -ISVADM option, place the installation management file in the default path for the -a option of the pkgadd command.
For details on the installation management file, see the documentation for the OS.

-ISVRESresponse-file-name ~ ((1 to 128 characters))
Specify the absolute path of the response file or the directory that contains the response file when you register the HP-UX or Solaris version of another company's software that requires user responses during installation.
When another company's software is distributed, the appropriate standard OS installation command is executed at the distribution-destination systems. At this time, the file or directory specified in the -ISVRES option is used for the following standard OS installation command option:
  • HP-UX: swinstall -cdirectory-name
  • Solaris: pkgadd -rfile-name
For details on the response file, see the documentation for the OS.

-ISVSOFT
Specify this as the first option when you register another company's software.

-kpassword ~ <uppercase alphabetic characters or numerics> ((1 to 8 characters))
Specify a password for registering resources with the managing server. Specify a password that has been set to identify a packager on the managing server.
  • When registering with UNIX JP1/Software Distribution Manager or UNIX JP1/Software Distribution Client (relay system)
    Enter the password you specified for PasswordForUpload in the settings file.
  • When registering with Windows JP1/Software Distribution Manager
    Enter the password you specified when you created the relational database. Do not enter any password unless you are using a relational database.
If you omit this parameter, JP1/Software Distribution Client displays a message prompting password input. If you want to input a password without having it displayed on the screen, enter a password in response to this message. If you specify option -Q, you must also specify the -k option.

-Linstallation-mode
Specify the installation mode for packages to be stored into the package storehouse.

G
GUI installation mode

B
Background installation mode
If you omit the -L option, JP1/Software Distribution Client assumes the background installation mode. The -L option is effective for distribution-destination systems of Windows. For non-Windows distribution-destination systems, JP1/Software Distribution Client ignores this option.

-mmanaging-host-name
If you want to perform packaging via two or more relay systems, specify the host name of the relay system that is directly connected to the managing server. You need not specify a managing host name if you are registering the package from the end workstation or from the relay system that is directly connected to the managing server.

-Nservice-name
In service-name, specify the service name for the managing server at which you want to package software.

-OSPATCH
Specify this option when you distribute OS patches. When you specify this option, package IDs are automatically acquired from the archive file names of the OS patches even if you do not specify the package IDs. The following rules apply when a package ID is automatically given:
  • Among the characters that are included in the archive file name of the OS patch, those that cannot be used in package ID are replaced by hyphens (-).
  • Upper-case alphabetic characters are used without change.
  • Lower-case alphabetic characters are replaced by corresponding upper-case alphabetic characters.
  • If the name of the OS patch archive file has more than 44 characters, the name is truncated following the 42nd character and two hyphens (--) are appended.
Note the following when you specify this option to distribute an OS patch:
  • You must specify the -d option as well when you specify this option.
  • When you package an OS patch, use a relative path name to specify the OS patch file in the -d option. When you want to package an AIX Maintenance Package, in the -d option, specify the relative path name of the directory that contains the AIX Maintenance Package.
  • If the AIX Maintenance Package that you want to package is an archive file, such as a tar file, unarchive the file before you perform packaging.
  • You cannot specify this option when the -D option is specified.

-Pinstallation-script-file-name
Specify the absolute pathname of an installation script file. If you omit specifying this parameter, JP1/Software Distribution Client executes packaging as a shared package, but does not register an installation script file.

-pprogram-name ~ ((1 to 50 characters))
Specify a general name to assign to the package of resources you want to package. Specify this name if you want to assign the package a generally known name other than the package ID. Unless you specify the -p option and a program name, the corresponding specification in the packaging-information file is effective. The specification in the -p option has priority over that in the packaging-information file. If you do not specify the name of the packaging-information file and if you omit the -p option, JP1/Software Distribution Client assumes blank characters. However, for another company's software, if you omit the -r and -p options, the program name is automatically generated.

-Q
Specify this option if you want JP1/Software Distribution Client to immediately quit the ongoing processing without waiting for the response in case a password input error or some other error should occur during packaging operation. If you specify the -Q option, you must not omit the -k option.
Specify the -Q option so that the command processing will terminate immediately in the following case:
  • You do not give a password to the command.
  • The password is incorrect.
  • Packaging for another distribution-destination system is being executed for the target group for packaging.
Also, you might specify the -Q option so that JP1/Software Distribution Client will quit the command execution without displaying the KDDM1544-Q message. This message prompts you to decide whether to overwrite the specified package if the same package ID exists.

-REBOOT
Specify this option to restart the operating system after you distribute the package. This option is enabled when Yes is specified for RebootPermission of the settings file.

-rpackage-ID ~ <uppercase alphabetic characters, numerics, hyphens, or underscores> ((1 to 44 characters))
Specify an ID for the package you want to register. The package ID must be unique in the network system. Unless you specify this option and a package ID, the package ID specified in the packaging-information file is effective. The specification in the -r option has priority over that in the packaging-information file. If you do not use the packaging-information file, always specify the -r option. However, you can omit the -r option when you register another company's software or an OS patch. If you omit the -r option, the package ID is automatically generated. For details on this automatic generation, see 2.2.3(2)(c) Automatic generation of package IDs in PART 1.

-tinstallation-date/time
Specify the date and time that the user program and user data will be installed, in YYYYMMDDHHMM format. When distributed to a PC, the packages will be installed automatically when the installation date/time is reached. When distributed to a workstation, you need to execute the rdsupt command. The package that has reached the installation date/time when the rdsupt command is executed will be installed. To automatically install the packages in the workstation, set GFAUTO in the operating-environment settings file.
When specifying the -t option, specify NETM_DM_GF in Generator.

-Vprerequisite-version ~ <uppercase alphabetic characters, numerics, or slants>((1 to 6 characters))
Specify a prerequisite version for distributing the package you want to register. The prerequisite version specified in the -V option has priority over that specified in the packaging-information file. If you omit specifying the -V option, the corresponding specification in the packaging-information file is effective.
If you specify 000000 as the prerequisite version parameter, JP1/Software Distribution Client unconditionally distributes the package, regardless of the prerequisite version. If this parameter specification exists in neither packaging-information file nor -V option, JP1/Software Distribution Client assumes blanks and distributes the package without checking the prerequisite version.
For another company's software, the -V option has no effect.

-vversion ~ < uppercase alphabetic characters, numerics, or slants>((1 to 6 characters))
Specify the version of the package you want to register. Unless you specify this option and a version, the corresponding specification in the packaging-information file is effective. The specification in the -v option has priority over that in the packaging-information file. If you do not specify the name of the packaging-information file and omit the -v option, JP1/Software Distribution Client assumes blank characters. However, for another company's software, if you omit the -r and -v options, the version is automatically generated.

packaging-information-file-name
Specify the absolute or relative pathname of the packaging-information file. If you omit specifying the packaging-information file parameter, user resource path parameter, and user resource path file parameter, JP1/Software Distribution Client assumes the following path of the packaging-information file as appropriate:
  • /NETMRDS/UPUPL/AC000000
  • /var/opt/NETMDMW/UPUPL/AC000000 (HP-UX)
If you do not use the packaging-information file, always specify the cabinet ID in the -g option. For a Hitachi program product or a user program and user data, if you do not use the packaging-information file, always specify the package ID in the -r option.

End code

End code Meaning
0 Terminated normally.
2 Free disk space is insufficient. Delete unnecessary files. If the space is still insufficient even after deleting unnecessary files on relay systems, initialize the temporary package storehouse by means of the rdsft -init command or rdsclr command.
3 Interface is invalid. Review the settings file or packaging-information file.
4 System error occurred. Contact system administrator.
5 Communication error occurred. Contact system administrator.
6 Internal error occurred. Contact system administrator.
7 Activation impossible. Contact system administrator.
8 Packaging of the same package ID has already been done or packaging of the same package ID for the same group is now being done from another terminal. In the former case, review the packaging-information file or delete the package registered by previous packaging. In the latter case, re-execute the command after a while.
9 An invalid package has been registered. Delete the invalid package.
10 Number of registered packages exceeds the limit. Contact the system administrator of the managing server.
11 Packaging is now being done from another terminal. Re-execute the command after a while.

Notes

Example

[Contents][Back][Next]

[Trademarks]

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