ca.portal.admin

Re: ADSA Response Security

Discussion created by ca.portal.admin on Oct 11, 2006
Chris: Sorry, but I don't know what ""option bits"" you are referring to.
Can you be more specific? Tim


----- Original message -----
From: ""Chris Hoelscher"" <chrishoelscher@INSIGHTBB.COM>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Tue, 10 Oct 2006 19:46:09 -0400
Subject: Re: ADSA Response Security

Tim,.

look at option bits 87 & 88 - seems to fit your situation


Chris Hoelscher
now in his 50th year!!!
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: ADSA Response Security
"At 15:53 10/11/2006, you wrote:
Chris:

As smart and knowledgable as I am, <ahem> I am a developer - not a DBA.
It sounds like you are saying that this issue of security not being
checked when the process code modifies AGR-CURRENT-RESPONSE is addressed
by these 2 apars? Yes?

Tim
if you are not a DBA, then you need to show the email i sent earlier
to your DBA if you decide this is the funcitonality you want




Chris Hoelscher
now in his 50th year!!!
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: SQL caching in local mode
"Kay,

You can see a difference when you also use the sysidms parameter BUFFERSTAT.
Set once SQL_CACHE_ENTRIES=0 and look in the syslst in the buffer statistics
for the catalog.
Second job : set SQL_CACHE_ENTRIES=500.
Luc

Luc De Naeyer
Corporate System Database Administrator for IDMS
Infoco (InformaticsColruyt)
T : +32 2 360 10 40
----- Original Message -----
From: ""Rozeboom, Kay [DAS]"" <KAY.ROZEBOOM@IOWA.GOV>
To: <IDMS-L@listserv.iuassn.com>
Sent: maandag 16 oktober 2006 18:58
Subject: SQL caching in local mode

I am trying to test SQL caching in local mode by using the new SYSIDMS
parameter ""SQL_CACHE_ENTRIES=nnn"". I cannot see any difference in CPU
used, even when I execute the exact same query 10,000 times. Is there
something else I need to do to turn on SQL caching for local mode? Is
there any way to tell whether or not it is turned on in local mode?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: SQL caching in local mode
"Thanks, Luc. That is helpful.

With further testing, I now believe that my problem is not with local
mode, but with COBOL in general.

When SQL caching is turned on, the following sources of SQL put entries
in the cache table (SYSCA.DSCCACHE):
- OCF
- BCF (CV mode)
- BCF (local mode)
- CA-IDMS Server

But the following do not:
- COBOL batch (CV mode)
- COBOL batch (local mode)
- DC-COBOL

The first obvious difference is that the first set issue dynamic SQL,
while the second set use pre-compiled access modules.
Is SQL caching not allowed for COBOL programs?

I have tried using a dynamically prepared SELECT in the COBOL programs,
but it doesn't seem to help. Maybe I am not doing it right. Has anyone
else gotten SQL caching to work for COBOL programs?

Outcomes