Regarding VAR.SQL restrictions, I thought you could customize what database it uses via the CONN object it is associated with. Have you tested the ability of associating it with CONN objects that point to different database technologies? (I could be mistaken)
I have an EXEC solution that passes three parameters. I defined them in the "variables" area of the job, and the process script begins with three :READ statements to capture them;
:READ &ESVC_Section#,,
:READ &ESVC_Key#,,
:READ &ESVC_Track#,,
------------------------------
Pete Wirfs
SAIF Corporation
Salem Oregon USA
------------------------------
Original Message:
Sent: 06-24-2020 09:53 AM
From: Harlow
Subject: VARA.EXEC and Parameters
Good day
I have tried the following on both of our Test (12.3.2) and Prod (12.3.1-HF1) environments.
I am trying to create a VARA.EXEC that runs a SQL job* (I've also tested this with a Windows job). Adding parameters doesn't seem to be working for me. I'm assuming the problem is somewhere between the keyboard and chair (and right in front of my face if history is anything to go by).
*We have the misfortune of having a split of MSSQL and Oracle databases, and a couple of other odds and ends due to COTS application restrictions and what not. It is my understanding that DB_SERVICE drives VARA.SQL and can only use one provider. So while this works great for our MSSQL databases, this does not work for other providers.
Edit: Forgot to add that the jobs are configured to inherit variables from their parents.
Here is what I have:
What exactly am I doing wrong here?
Thanks!