Best practices for registering UDXs that use SPUPads

When you register UDXs that take advantage of SPUPad features, keep in mind the following notes:

• Make sure that you register SPUPad UDXs as NOT FENCED; fenced UDXs cannot use SPUPads.
• Make sure that you register a UDF as NOT DETERMINISTIC when the UDF uses a SPUPad.
• Make sure that you add the memory requirements of the SPUPad to the memory needs of the UDX in the MAXIMUM MEMORY argument. You need to add in the SPUPad memory for any UDX that creates a SPUPad and any UDX that uses a SPUPad created by another UDX. Starting in release 6.0, you can specify a wider range of values for the MAXIMUM MEMORY input. The previous limit was 10 MB. Use caution with the SPUPad memory consumption, as large SPUPads can affect the system performance and result in out-of-memory errors for your UDXs.