SQLJ.REMOVE_JAR

Authorization

The privilege held by the authorization ID of the CALL statement must include at least one of the following for the SYSJARCONTENTS and SYSJAROBJECTS catalog tables:

• The following system authorities:
  • The SELECT and DELETE privileges on the table
  • The system authority *EXECUTE on library QSYS2
• Administrative authority

The privilege held by the authorization ID of the CALL statement must also have the following authority.

• *OBJMGT authority to the JAR file being removed. The JAR file is named /QIBM/UserData/OS400/SQLLib/Function/jar/schema/jarfile.

Adopted authority cannot be used for this authority.

Syntax

     >>-CALL--SQLJ.REMOVE_JAR--(--'jar-id'--,--undeploy--)----------><

Description

jar-id

The JAR identifier of the JAR file that is to be removed from the database.

undeploy

The value used to describe the remove_action of the deployment descriptor file. If this integer is a non-zero value, then the remove_actions of a deployment descriptor file should be run at the end of the install_jar procedure. The current version of DB2^® UDB for iSeries™ only supports a value of zero.

Example

The following command is issued from an SQL interactive session:

     CALL SQLJ.REMOVE_JAR('myProc_jar', 0)

The JAR file myProc_jar is removed from the database.