The value \"\" in an uproc variable on duas v5 is not interpreted the same way after upgrading to duas v6
book
Article ID: 85444
calendar_today
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message : Example of v5 on the job log:
_!================================================ _!** $!** PROCEDURE .. : TEST_VAR $!** VERSION .....: 000 $!** EXECUTION .. : 0000024 _!** _!** DATE TRAIT.. : 26/01/2015 _!** _!------------------------------------------------ $!** PARAMETRES.. : AUCUN _!------------------------------------------------ _!** VARIABLES VAR1 :\"\" _!================================================ + echo value of VAR1 before is "" value of VAR1 before is "" + /orsyp/cdp/S56001/exec/uxset var VAR1="" + echo value of VAR1 after is "" value of VAR1 after is ""
Example on 6.3.23:
C00-SUPPORT-SITE DEBUT C00-SUPPORT-SITE WSPGM-CODNOEUD frstaix612 _!================================================ _!** $!** PROCEDURE .. : TEST_VAR $!** VERSION .....: 000 $!** EXECUTION .. : 0065862 _!** _!** PROCESS DATE : 01/26/2015 _!** _!------------------------------------------------ $!** PARAMETERS. : None _!------------------------------------------------ _!** VARIABLES VAR1 :\"\" _!------------------------------------------------ $!** INHERITANCE VARIABLES _!================================================ + echo value VAR1 before is \\ value VAR1 before is \ + /orsyp/MIGROS_frstaix612/bin/uxset var VAR1="" + echo value VAR1 after is \\ value VAR1 after is \ + exit 0
Description :The value \"\" in an uproc variable on duas v5 is not interpreted the same way after upgrading to duas v6
Cause
Cause type: Defect Root Cause: N/A
Environment
OS: All Unix
Resolution
The value of an uproc variable on v5.6 with \" is not interpreted the same way on v6, on unix. In v5.6, double quotes need to be escaped in the value of the uproc variable, whereas in v6 there is no need to do so. This has an impact on uprocs after upgrading from 5 to 6. A new node setting has been added to v6: U_BATCH_ESCAPE_DQ (in technical settings). When this node setting is set to Y, there is no need to escape the double quotes in uproc variables (current v6 behaviour). When it is set to N, double quotes need to be escaped (current v5 behaviour). For a fresh v6 install, the node setting is set to Y During an upgrade from 5 to 6, the node setting is set to N to keep the v5 behaviour.
Also, the check tool checks if there are uproc variables with escaped double quotes.