Action on Jobs in Event Wait or SAP uprocs fail if MU switches

Document ID : KB000084663
Last Modified Date : 17/05/2018
Show Technical Document Details
Issue:
Error Message :
When some Actions can't be performed on Jobs in status Event Wait, a popup error appears on UVC with the message:
"The Related Object could not be found"

When the issue concerns multi-node sessions launching SAP uprocs, the following kind of error appears in the job log:

Cannot find launch: owls_api_fla_read returns 600
Cannot update launch: o_upd_sap_launch returns 600
 

First symptom:

The following actions (either from the Command Line or by UVC):

Update / View History Trace / Bypass Conditions will not work.

The issue can only occur if all of the following conditions are met:

  1. Launching a task based on a session where the MU changes in the middle of the session ( i.e. UPR_1 – MU_1 , UPR_2 – MU_2)
  2. A uproc within the session (other than the Header) has a condition not met, so it remains in status Event Wait
  3. This uproc in Event Wait has no Specific Task with the corresponding MU
  4. The node is on version 6.8.xx

Second symptom:

SAP Uprocs (SAP_XBP2, SAP_PCHAIN, or on any CL_INT, CL_EXT Uprocs) that execute an SAP command, for instance, such as:

‘uxstr sapapi jobname=...’ abort with the error "Cannot find launch: owls_api_fla_read returns 600"

The issue can only occur if all of the following conditions are met:

  1. The SAP uprocs are inside sessions where MU changes and the SAP Uprocs is executed after the MU change.
  2. The session is launched via a task!  When launching the session outside a task, it works correctly.
Environment:
OS: All
OS Version: N/A
Cause:
Cause type:
Defect
Root Cause: Since version 6.8.01, Dollar Universe was looking for a task with invalid settings (invalid MU) to retrieve the Launch Variables, since it did not exist, jobs would fail.
Resolution:
Update to a fix version listed below or a newer version if available.​

Fix Status: Released

Fix Version(s):
Dollar Universe 6.8.24 - Available
Additional Information:
Workaround :
Several workarounds exist for this kind of issue.
  1. Launch the session without a task, via command 'uxadd fla
  2. Create a specific task (provoked) for the related uproc in the session.
  3. If none of the above is feasible, downgrade the node to version 6.7.41 or below