The following was discovered when performing a manual launch of a Session in certain circumstances:
1) Create a session (ex: 0015461) with a header, body and trailer uprocs (ex: 0015461_H, 0015461_B, and 0015461_T).
2) Set a variable for 0015461_B (ex: PARAMETER1=GoodVar)
3) Set the script of 0015461_B to echo $PARAMETER1
4) In job runs view, create a manual launch of the session 0015461. Check the job log and you should see 'GoodVar'
5) In job runs view, create a manual launch of the uproc 0015461_B. Check the job log and you should see 'GoodVar'
6) Create a Scheduled Task (ex: 0015461_PLANNED) that executes the session starting at 0015461_H. Create a Specific Task (ex: 0015461_PROVOKED) within this Scheduled Task that should run 0015461_B. The Specific Task should have a variable set to PARAMETER1=BadVar.
7) When 0015461_PLANNED executes, 0015461_B will naturally echo 'BadVar'.
8) Now that the Tasks are created, go to job runs view and create a new launch based on only the uproc 0015461_B. It will echo 'GoodVar'.
9) Next, create a new launch based on the session 0015461. The job log will echo 'BadVar'.
This should not happen as no Task was referenced, so why would the variable defined in the Specific Task 0015461_PROVOKED appear in a manual run?
This occurs as well when a Specific Task is removed from the Main Task - Specific Tasks list, when executed the main task, if the specific task associated is still enabled and exists on the target node, it will be executed.
Release : 6.x and 7.x
Component: Dollar Universe
Defect introduced in Dollar Universe 220.127.116.11 version, as long as a specific provoked or optional task exists for a Uproc inside a Session, it will be used no matter if it's attached to the Main Task or if the launch came from the Main Task or a Session.
Delete or Disable the provoked Task if no longer attached to the Main Task or no longer being used.
The issue has been confirmed to be a bug by our Dev team.
A fix will be provided in a future version.