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.
The Function GET_ATT_SUBSTR does not work properly when parsing the first Parameter
Article ID: 87518
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
The function GET_ATT_SUBSTR does not work properly when parsing the first parameter.
Investigation
In the process tab of the Notification Object:
Then, the Archive 1 contains SYS;NET;ERP.
Results
Actual: The value for &POD# is SYS;NET;ERP
Expected: The value of &POD# should be SYS
N/A
The function GET_ATT_SUBSTR does not work properly when parsing the first parameter.
Investigation
In the process tab of the Notification Object:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:SET &POD#=GET_ATT_SUBSTR(ARCHIVE_KEY1,1,3)
:P &POD#
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:SET &POD#=GET_ATT_SUBSTR(ARCHIVE_KEY1,1,3)
:P &POD#
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Then, the Archive 1 contains SYS;NET;ERP.
Results
Actual: The value for &POD# is SYS;NET;ERP
Expected: The value of &POD# should be SYS
Cause
Cause type:
By design
Root Cause: This is normal behavior for GET_ATT_SUBSTR. It can only be used with the body of the Notification.
By design
Root Cause: This is normal behavior for GET_ATT_SUBSTR. It can only be used with the body of the Notification.
Environment
OS Version: N/A
Resolution
If you need to retrieve the archive attributes, you must use GET_ATT and SUBSTR functions.
Example:
:SET &POD#=GET_ATT(ARCHIVE_KEY1) :P &POD# :SET &SUB#=SUBSTR(&POD#,1,3) :P &SUB#
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
