Problem Note 63238: A SAS® Data Studio 2.2 data plan that contains a parsing transformation fails with errors in SAS® Viya® 3.3
A data plan in SAS Data Studio 2.2 that contains a parsing transformation might result in incorrect code. The log for the Data Plans services in SAS Viya 3.4 can show an error similar to the following:
ERROR: Length of argument (1064) is greater than the maximum allowed by function (1024).
ERROR: Invalid parsed input.
NOTE: Argument 1 to function DQPARSETOKENGET(data,token,definition,locale) at line x column yyy is invalid.
This problem occurs because the size of the returned parsedValue variable is the default length, and that length is not sufficient.
The data, token, definition, and locale placeholders in the message above correspond to values that you select in the properties of the parsing transformation. Here is an example:
NOTE: Argument 1 to function DQPARSETOKENGET('Mr./=/John D'[12 of 198 characters shown],'Family Name','Name','ENUSA') at line 3 column 106 is invalid.
A workaround is to add an empty string column named parsedValue to the input data set. The variable should define an appropriate length for the argument.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Viya | Microsoft Windows Server 2012 R2 Std | 3.4 | 3.5 | | Viya |
Microsoft Windows Server 2016 | 3.4 | 3.5 | | |
Linux for x64 | 3.4 | 3.5 | | Viya |
Microsoft Windows Server 2012 R2 Datacenter | 3.4 | 3.5 | | Viya |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
A parsing transformation in a SAS Data Studio 2.2 data plan in SAS Viya 3.4 can produce incorrect code. You then see multiple error messages after you execute the data plan.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2018-12-05 09:16:24 |
Date Created: | 2018-11-15 14:36:04 |