SQL/MX Guide to Stored Procedures in Java (G06.24+, H06.03+)

Managing SPJs in NonStop SQL/MX
HP NonStop SQL/MX Guide to Stored Procedures in Java—523727-004
6-20
Copying Java Classes to the Remote Node
Advantages of Copying the Java Classes
The advantage of this approach is that there are fewer cross-node dependencies. If the
network is disconnected or if one node goes down (for example, \NODEA), a statically
compiled application can still execute the SPJ on the remaining node (for example,
\NODEB), as long as the procedure label of the SPJ is still available.
The procedure label is available if it is located on the same node (in this case,
\NODEB) as the calling application or if it is located on a remote node that is still
connected and visible (for example, \NODEC). If the procedure label is unavailable (for
example, if it is on \NODEA), the CALL statement that invokes the SPJ will fail. For
more information about the procedure label, see Naming the Procedure Label on
page 4-10 and Showing the Procedure Label on page 6-11.
Currently, NonStop SQL/MX has limited local node autonomy because it disallows the
replication of metadata from one node to another. For more information about the
limitations on local node autonomy, see the SQL/MX Installation and Management
Guide.
Disadvantages of Copying the Java Classes
The disadvantage of this approach is that the Java classes must be maintained on
more than one node. If you change and recompile the Java class on one node, you
must do the same on the other node. Otherwise, the SPJ might behave inconsistently
in a distributed database environment.