IDMS

I am trying to create a 'LANGUAGE IS SQL' procedure which dynamically creates an ADS dialog. The dialog is getting created but I'm getting the following error during compilation. Our DBA hasn't figured it out yet so I'm hoping someone lese may have experienced this issue.

The error is:

USER IS NOT AUTHORIZED FOR ACCESS TO THIS DIALOG

Reason:

Dictionary has option "AUTHORIZATION IS ON FOR ADS" but ADSOCDGN was not provided with the ID of a user in the dictionary for which a "MOD PROGRAM <dialog name> INCLUDE USER <NAME> IS RESPONSIBLE FOR UPDATE" has been done.

Module:

ADSOCDGN

Do you have public access for all on the program:

*+   ADD                                           

*+   PROGRAM NAME IS A135P4D VERSION IS 1

*+       NUMBER OF TIMES COMPILED IS 8             

*+       DESCRIPTION IS 'ADS DIALOG'               

*+       PUBLIC ACCESS IS ALLOWED FOR ALL         

Hi Steve, Thanks for responding.  I tried creating the dialog in advance of creating the procedure but got an error.  Our DBA says it has to do with ADS security.

The dialog gets created dynamically when the procedure is created.  Could it be a SYSGEN setting?

Thanks,

Margaret

Margaret,

I have a dialog auto-created by a function but it is in a dictionary where security for ADS is off.  When I display the program in IDD it shows:

so I'm guessing that could be an issue for ADS security.  Maybe if you do a manual add program with the public access that Steve suggested and then try to drop and create the procedure again you will get a different result?

John

John,

I think you're right.  Our DBA said he did get it to work by disabling some ADS security.  I'm wondering if it needs the same security granted as dialogs for ADS procedures.

I guess that would make sense.

Thanks, John,

Margaret

This problem has been resolved.  It required an APAR from CA which we have received and tested.

Thanks,

Margaret

Hi Margaret,

Out of curiosity, what is the apar number ?

Thanks,

Laura

Hi Laura,

I went back and looked at the email from the DBA and he said it was a test APAR, whatever that means.

He didn't specify a number and he's out until the end of the month.

He did create a temporary load library for the APAR so I'm guessing once we're sure the problem is resolved, CA will make a permanent fix.  Not being a DBA, I'm not sure how that works.  We were just given a different load library to use for creation of these procedures.

Will let you know when I find out more.

Thanks,

Margaret

I am guessing if you know the load module name and the library it is in, browse the load module member, look for literal TR – record the 5 numbers the come after, you could identify the test APAR number – this wold wllo other sites that have a similar need to request the test apar by name (nt necessary, perhaps, but it might save some time)

Chris hoelscher

Technology Architect

Database Infrastructure Services

Technology Solution Services

123 East Main Street

Louisville, KY 40202

choelscher@humana.com<mailto:choelscher@humana.com>

Humana.com

(502) 714-8615

(502) 476-2538

Test PTF was TR83787.

Thanks, Bob!!

Hi all,

Indeed, the fix is  TR83787, and it's for IDMS 18.0.

It's still a testfix, not published yet.

The fix applies to module ADSOCDGN. You can check this by means of a LOOK PROGRAM=ADSOCDGN or DCMT DIS MODID ADSOCDGN

I would recommend making the fix permanent.  These procedures are great!!  Though I would prefer to use an ADS dialog, for those not versed in ADS, these procedures can provide all the 'brains' that an ADS dialog can when extracting data from IDMS to send to the web.  Someone who is familiar with SQL stored procedures will be easily able to understand the code.  That is the reason we're using them.  However, they generate an ADS dialog when they are compiled so they are basically an ADS procedure.  Pretty slick!! 

Just wondering about the IUA/CA Technical Conference next spring - if maybe you would like to share some of what you have learned about SQL Procedures and what you have used them for from an application developer's point of view? I think that this would make an excellent user session! Any interest? Take care - cheers - GaryC

I'd be happy to, Gary!!  Thanks for the suggestion!

Margaret

Just curious if this fix has been made permanent and published yet.

Haven't heard any more about it.

Thanks,

Margaret

Hi Margaret,

    Yes, the fix was published back in the September-2016 timeframe under APAR RO83787.

Thanks,

Dave D.

Ooops...    meant Sept-2015...