SQLJ.REPLACE_JAR stored procedure

SQLJ.REPLACE_JAR replaces an existing JAR file in the local DB2® catalog.

SQLJ.REPLACE_JAR authorization

Privilege set: If the CALL statement is embedded in an application program, the privilege set consists of the privileges that are held by the authorization ID of the owner of the plan or package. If the statement is dynamically prepared, the privilege set consists of the privileges that are held by the authorization IDs of the process.

For calling SQLJ.REPLACE_JAR, the privilege set must include at least one of the following items:
  • EXECUTE privilege on SQLJ.REPLACE_JAR
  • Ownership of SQLJ.REPLACE_JAR
  • SYSADM authority
The privilege set must also include the authority to replace a JAR, which consists of at least one of the following items:
  • Ownership of the JAR
  • ALTERIN privilege on the schema of the JAR

    The authorization ID that matches the schema name implicitly has the ALTERIN privilege on the schema.

  • SYSADM or SYSCTRL authority

SQLJ.REPLACE_JAR syntax

>>-CALL--SQLJ.REPLACE_JAR--(--url,--JAR-name--)----------------><

SQLJ.REPLACE_JAR parameters

url
A VARCHAR(1024) input parameter that identifies the z/OS® UNIX System Services full path name for the JAR file that replaces the existing JAR file in the DB2 catalog. The format is file://path-name or file:/path-name.
JAR-name
A VARCHAR(257) input parameter that contains the DB2 name of the JAR, in the form schema.JAR-id or JAR-id. JAR-name is the name that you use when you refer to the JAR in SQL statements. If you omit schema, DB2 uses the SQL authorization ID that is in the CURRENT SCHEMA special register.

SQLJ.REPLACE_JAR example

Suppose that you want to replace a previously installed JAR file that is named DB2INST3.BUILDPLAN with the JAR file that is in path /u/db2inst3/apps/BUILDPLAN2/BUILDPLAN.jar. Use a CALL statement similar to this one.

CALL SQLJ.REPLACE_JAR('file:/u/db2inst3/apps/BUILDPLAN2/BUILDPLAN.jar',
 'DB2INST3.BUILDPLAN')