Author Topic: zOD V10.1.0.5 - not using the modified sql in the arsutbl C exit  (Read 1260 times)

HenryJohansen

  • Newbie
  • *
  • Posts: 1
    • View Profile
zOD V10.1.0.5 - not using the modified sql in the arsutbl C exit
« on: February 28, 2020, 07:29:11 AM »
I currently writing a 64-bit arsutbl exit in C on z/OS where I'm changing the SQL for CREATE INDEX to CREATE UNIQUE INDEX for a particular index key. And set the *created = 0 in order to let CMOD create the index with the modified SQL.
The output from the "printf-trace" in the ARSSOCKD stc shows the exit being invoked and it also displaying the original SQLs and the changed SQL (both variabel sql from ArcChar *sql declaration).
But in DB2 I can see the original SQL has been invoked instead for the modified SQL.

Any suggestions what's wrong?

Regards
Henry

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: zOD V10.1.0.5 - not using the modified sql in the arsutbl C exit
« Reply #1 on: February 28, 2020, 09:51:06 PM »
This question was split from another topic.  Please ask questions in a new post, where they can get the most visibility, and have the best chance of being answered by others.  :)
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR