Dynamic Relational Stage resolution of $PARM parameters

[gsherry1]

Hello Forum,

I've placed several variables like $DB_USER, $DB_NAME, $DB_PASS in my project parameter file via administrator, but when I try to use these in the Dynamic Relational Stage, I get a variety of errors including the following:

TargetTable: When processing argument -inlinkpropsWhen processing input link property list: {
TABLE='#$DB_NAME#.testtable',
GENSQL='Yes',
USERSQL='INSERT INTO tests.testtable (key,data) VALUES (:1,:2)',
ARRAYSIZE=1,
TRANSSIZE=0,
CREATETABLE='No',
GENCREATEDDL='Yes',
USERCREATEDDL='CREATE TABLE tests.testtable (
key INTEGER NOT NULL,
data VARCHAR(100) NOT NULL
)
',
DROPTABLE='No',
GENDROPDDL='Yes',
USERDROPDDL='DROP TABLE DODELETE='No',
DOUPDATE='Insert rows',
TREATWARNASFATAL='NO',
TX_ISO_LEVEL='Read Committed',
CONTBEFORESQL='YES',
CONTAFTERSQL='YES',
DSTxnSize=0,
DSSQLType={key=4, text=12},
DSSchema='record
(
key:int32;
text:string[max=100];
)'
} is not a valid property list: Expected "," or "}", got: "No"
Encountered <eof> while seeking end of proplist

It is clear above that #$DB_NAME# is not being resolved properly in all contexts. It works if I use job parameters non resident in the dsenv file. ei No $ sign.

Is there some known issue with using such parameters in the DRS? Any fixes/workarounds?

Thanks,

Greg

[roy]

Hi,
There is an APT variable that enables special char convert use it from the prarameter tab of your job's properties page, without it you can't use any parameters inside the DRS stage.

IHTH,