The pdjarsync command manipulates JAR files.

There are the following types of JAR file manipulation:

• Re-registration of a JAR file between hosts (applicable to a HiRDB parallel server configuration only)
• Registration of a JAR file
• Re-registration of a JAR file
• Deletion of a JAR file
• Display of a list of JAR files

This command is used when Java stored procedures or Java stored functions are used.

HiRDB administrator

(a) HiRDB single server configuration

 
 pdjarsync [{-I|-R|-D| -L } ]
            [-u authorization-identifier [,authorization-identifier]...]
            [-f JAR-filename]
 

(b) HiRDB parallel server configuration

 
 pdjarsync [{-S|-I|-R|-D| -L}]
            [-x host-name[,host-name]...]
            [-u authorization-identifier [,authorization-identifier]...]
            [-f JAR-filename]
 

(a) {-S|-I|-R|-D| -L}

Specifies the type of JAR file manipulation.

-S

For a HiRDB parallel server configuration, this option re-registers the specified JAR file between hosts.

The command re-registers a JAR file in the host specified with the -x option into the server machine in the HiRDB environment. If the -x option is omitted, the command re-registers a JAR file in the server machine containing the dictionary server into the server machine in the HiRDB environment.

Specify the -S option if you have modified the HiRDB server configuration (such as when increasing the number of server machines) or conducted system switchover.

-I

This option registers the specified JAR file.

If you specify this option, be sure to specify the -u and -f options.

If the specified JAR file has already been registered, the command results in an error.

-R

This option re-registers the specified JAR file.

If the specified JAR file has already been registered, the command overwrites the registered JAR file.

If you specify this option, be sure to specify the -u and -f options.

-D

This option deletes the specified JAR file.

If you specify this option, be sure to specify the -u and -f options.

If the specified JAR file has not been registered, the command results in an error.

If the pdjarsync command terminates abnormally, a JAR file under write operation may remain in the system. In this case, specify the -d option to delete such remaining JAR files.

-L

This option displays a list of registered JAR files.

The table below shows the relationship between the JAR file manipulation type and other options.

Table 2-12 Relationship between JAR file manipulation type and other options

Legend:

M: Mandatory

O: Optional

#: If specifying the -x option, specify only one host name.

(b) -x host-name[,host-name]

If specifying the -S option, specify only one host name that is to be the origin of re-registration. If this option is omitted, the system assumes the host where the dictionary server is located.

If you specify an option other than -S, specify the name of the host being manipulated. If omitted, the system assumes all hosts in the HiRDB environment.

(c) -u authorization-identifier[,authorization-identifier]...

Specify the authorization identifier of the user who is to manipulate the JAR file.

If you have specified the -I, -R, and -D options, be sure to specify this option also.

For the authorization identifier, you cannot specify MASTER or HiRDB.

(d) -f JAR-filename

Specify the name of the JAR file to be manipulated.

If you have specified the -I, -R, and -D options, be sure to specify this option also.

If you specify the -S and -L options but omit this option, the system assumes all JAR files that have been registered.

The JAR files are stored in the directory specified with the pd_java_archive_directory operand in the system definitions.

1. You can execute the pdjarsync command whether or not HiRDB is active.
2. Execute the pdjarsync command at the server machine containing the single server or the server machine where the system manager is located.
3. Do not execute more than one pdjarsync command at any one time.

1. If you execute the INSTALL JAR, REPLACE JAR, or REMOVE JAR SQL statement, the pdjarsync command is executed internally. In these cases, the pdjarsync command is executed from the single server or the front-end server.
2. The following shows the pdjarsync command's return code:
   0: Normal termination
   4: Abnormal termination (for registration or re-registration, the specified JAR has already been registered; for deletion, the specified JAR file has not been registered)
   8: Abnormal termination
   

When the -L option is specified in the pdjarsync command or the -L option is assumed by default, the following information is output:

 
HOSTNAME(aabbcc)  DATE        TIME       SIZE    OWNER   FILE
dd...d            eeee/ff/gg  hh:ii:jj   kk...k  ll...l  mm...m
   :                   :          :         :       :       :
 

Explanation

aabbcc

Time the pdjarsync command was executed

dd...d

Host name

eeee/ff/gg

Date of the JAR file^#

hh:ii:jj

Time of the JAR file^#

kk...k

Size of the JAR file (in bytes)

ll...l

Owner of the JAR file

mm...m

Name of the JAR file

#: If an SQL statement (INSTALL JAR, REPLACE JAR) or JDBC method was used to register or re-register the JAR file, this is the date and time the SQL statement or JDBC method was executed. If the pdjarsync command was used to register or re-register the JAR file, this is the date and time of the registered or re-registered JAR file.