ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Report parsing not possible when using RA JMS Agent.
Article ID: 87871
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
In a JMS Job when the Report is parsed and the Values are saved with the function 'Save as a Variable' , the values must be passed on again in Postscript with PSET first before they are available in successor Jobs in a Workflow.
This should not be the case, once the Report is parsed and saved as a variable, the values should be automatically available, and the second step whereby the values are passed in Postscript via PSET is not necessary.
N/A
In a JMS Job when the Report is parsed and the Values are saved with the function 'Save as a Variable' , the values must be passed on again in Postscript with PSET first before they are available in successor Jobs in a Workflow.
This should not be the case, once the Report is parsed and saved as a variable, the values should be automatically available, and the second step whereby the values are passed in Postscript via PSET is not necessary.
Cause
Cause type:
Defect
Root Cause: Missing line of code to set "hasParent" on the ThreadContext.
Defect
Root Cause: Missing line of code to set "hasParent" on the ThreadContext.
Environment
Release: WAASER99000-1.0-Automic Workload Automation-Services
Component:
Component:
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: Released
Fix Version(s):
RA JMS 2.0.0 - Available
Fix Status: Released
Fix Version(s):
RA JMS 2.0.0 - Available
Additional Information
Workaround :
Use PSET in Postscript to pass the values.
Use PSET in Postscript to pass the values.
Feedback
Yes
No
Powered by
