Pathway/iTS SCUP Reference Manual

SCUP Commands
HP NonStop Pathway/iTS SCUP Reference Manual—520269-002
2-22
CONVERT Command
1. Comment out the statements of the method in the generated Java file after the
return statement, then recompile the Java code.
•
No such method error
Cause: Occasionally, the converter cannot distinguish between the section name
and the first paragraph name within the section, and generates the error No such
method.
Recovery: Manually check the generated code. If a method exists with the same
name as the section name or the first paragraph name, replace the method call
with the name of the section or first paragraph.
•
InvocationTargetException
Cause: Occasionally a converted application throws a InvocationTargetException
to the caller of the program unit. This can occur because SCOBOL handles the ON
ERROR clause of BEGIN-TRANSACTION differently from the generated Java
code and may occur if the same application is run in multiple browsers on the
same Windows desktop.
After the execution of the ON ERROR clause in SCOBOL, execution continues to
the statement next to the BEGIN-TRANSACTION statement. However, in the
generated Java code, control returns to the caller of the program unit.
BEGIN-TRANSACTION, SEND, and END-TRANSACTION statements are host-
delegated tasks that are performed by the gateway (PathTCP3 and the SCOBOL
GATEWAY) on the NonStop system. If the link between the client and the gateway
is abnormally terminated (for example, due to the loss of the socket link with the
client or due to the abnormal termination of TMF), the applet executing the Java
code executes the ON ERROR clause much like SCOBOL would execute it. In
other words, if the link is terminated when the client is in transaction mode
(between BEGIN-TRANSACTION and END-TRANSACTION statements), then the
ON ERROR clause is executed by the client. If the ON ERROR clause is not
present, the applet throws error 3301, Transaction Error, and the application stops.
After executing the ON ERROR clause, an exception (ScobolTxnException) is
thrown to the caller of the program unit, which catches it as an
InvocationTargetException. The control, therefore, returns to where the program
unit was invoked.
Recovery:
•
From a single Windows desktop, run the application in a single browser. To
restart the application, close the browser and then restart it.
•
Or, modify the catch block of the CALL statement in the generated Java code
to catch the exception ScobolTxnException. Add code in the catch block to
continue the execution in a more appropriate manner.
•
Purge error for file old_system_name.vol.subvol.htmlfile (file-system error)