6.1.2 Notes on using plug-ins

Organization of this subsection
(1) HiRDB setup/startup conditions and availability of plug-ins
(2) Availability of plug-ins in the event of plug-in initialization error
(3) Availability of plug-ins depending on the unit

(1) HiRDB setup/startup conditions and availability of plug-ins

Table 6-1 shows the HiRDB (unit) setup/startup conditions and availability of plug-ins.

Table 6-1 HiRDB (unit) startup conditions and availability of plug-ins

Plug-in utilization declaration (pdplugin operand)Registration of plug-in (pdplgrgst)Plug-in initialization errorWhether or not unit can be startedAvailability of plug-in
Not specifiedRegisteredNoneS[Figure]
OccurredS[Figure]
Not registeredNoneS[Figure]
OccurredS[Figure]
SpecifiedRegisteredNoneSS
OccurredS[Figure]
Not registeredNoneS[Figure]
OccurredS[Figure]

S: Unit can be started, and plug-in can be used.

[Figure]: Unit cannot be started, nor can plug-in be used.

(2) Availability of plug-ins in the event of plug-in initialization error

Plug-ins are initialized automatically during HiRDB startup. If multiple pdplugin operands are specified in the system common definition and at least one of them results in a plug-in initialization error, none of the plug-ins in the unit can be used.

(3) Availability of plug-ins depending on the unit

The availability of plug-ins depends on conditions at the unit in the following cases:

An SQL statement that calls only the available plug-ins will execute successfully; however, if it attempts to call even one unavailable plug-in, execution of the SQL statement will fail.