ca.portal.admin

Re: No commits, SOS, dynamic lock table allocation, syslocks

Discussion created by ca.portal.admin on Jul 6, 2006
Think of doing a binary search for active, and the cost of it. Now
consider doing 2 (second allocation) if the key isn't in the first
table, or a third search for the item if not in the 1st or 2nd table.
This basicly would be the cost.

P.S. If there is room to allocate the extended SYSLOCK table out of the
255 pool, IDMS will do so, if not an attempt is made to pool 0, and most
likely no pool 0 will have room for an extend syslock table.

Edward A. Timm
Sallie Mae, Senior Database Analyst
ETIMM@salliemae.com
(317) 596-1182
Fax (317) 595-1494
PetzoldL@Aetna.Com 07/06/2006 10:07:29 AM >>>
I know the pat answer to SOS in pool 0 conditions is to either
increase
the commit frequency and or sysgen more syslocks. But why is
increasing
syslocks so much more efficient then dynamic lock allocation? What is
it about dynamic lock allocation that is so wasteful? And why does it
have to come out of pool 0 instead of some above the line pool, like
255? Does anyone have a technical explanation? I am getting the
sneaking suspicion that there is a bug in dynamic lock allocation.

Lutz Petzold


-----------------------------------------
This e-mail may contain confidential or privileged information. If
you think you have received this
e-mail in error, please advise the sender by reply
e-mail and then delete this e-mail immediately. Thank you. Aetna


This E-Mail has been scanned for viruses.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
ADS SQL Access Module problems
"Hello All:

Kay Rozeboom and I are having difficulty getting an ADS dialog to access
an SQL access module. I'm sure my explanation will create more
questions,
but the gist is this:

ADS dialog with embedded SQL which can be executed successfully in OCF.
Compiled the dialog, the created the access module in the same schema
indicated in ADSC Database Specifications screen.

When the dialog is executed, it always returns an SQLSTATE=42503
(42=Syntax error.... 503=Authorization failure) and SQL error
message DB00552 1 T26018 C-4M321: Missing authorization for <access-
module name>.

What we can't figure out is why?

Thanks,

Tim Gortner
State of Iowa
Department of Human Services

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: ADS SQL Access Module problems
"Alan:

Since I have authority on the underlying tables and I can CREATE the
access module, I assumed I would have EXECUTE authority too. Perhaps we
have an incorrect assumption. I received no warning message when the
access module was created - only when executed. This is currently
connecting to a TEST dictionary in which I can do most things.

Thanks for the tip.

Tim Gortner
==============================================
The SQL Option Reference states:

8.16.2 Authorization To issue a CREATE ACCESS MODULE statement, you must
own the schema with which the access module is being associated or
hold the CREATE privilege on the named access module.

In addition to enforcing this authorization requirement, Advantage CA-
IDMS also validates the access module owner's authority to execute every
DML statement in the RCMs included in the access module if the
dictionary to which the SQL session is connected is controlled by
Advantage CA-IDMS internal security.

If the access module owner does not hold the authority to execute a DML
statement in the access module, when the access module is created, a
warning is issued. If the owner still lacks a necessary authority when
the access module is executed, an error is returned.

8-64 Advantage CA-IDMS Database SQL Option Reference Guide

================================================
----- Original message -----
From: ""Alan Fields"" <Alan_Fields@VFC.COM>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Thu, 6 Jul 2006 17:04:51 -0400
Subject: Re: ADS SQL Access Module problems

Access modules are securable resources (or not depending on what the
SRTT says). The signed on user executing the ADS dialog (or any other
program for that matter) requires the EXECUTE privilege on the access
module and appropriate privileges on the underlying tables.

Alan Fields VF Corporation Greensboro, NC 336-424-4773
Alan_Fields@vfc.com


IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM> wrote on
07/06/2006 04:44:40 PM:
Hello All:
Kay Rozeboom and I are having difficulty getting an ADS dialog to
access an SQL access module. I'm sure my explanation will create
more questions, but the gist is this:
ADS dialog with embedded SQL which can be executed successfully in
OCF. Compiled the dialog, the created the access module in the same
schema indicated in ADSC Database Specifications screen.
When the dialog is executed, it always returns an SQLSTATE=42503
(42=Syntax error.... 503=Authorization failure) and SQL error
message DB00552 1 T26018 C-4M321: Missing authorization for <access-
module name>.
What we can't figure out is why?
Thanks,
Tim Gortner State of Iowa Department of Human Services
This email is intended solely for the use of the individual(s) to whom
it is addressed and may contain information that is privileged,
confidential or otherwise required to be protected from disclosure. If
the reader of this email is not the intended recipient, you are hereby
notified that any dissemination, distribution, copying or other use of
this communication or its attachments is strictly prohibited. If you
have received this communication in error, please delete it as well as
all copies or backups of it entirely from your email system and notify
me that you received this email in error. Thank you.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: ADS SQL Access Module problems
"Tim,
You do have to GRANT authority for DEFINE, ACCESS and EXECUTE for each access module or all for a specific schema. This was a reall pain in the butt when we were implementing our application. I'm sure you already know this but all dialogs within an application thread must have the same subschema and access module name.
Margaret


-----Original Message-----
From: Tim Gortner [mailTo:idms-l@LOOKOUTPCWORKS.COM]
Sent: Thursday, July 6, 2006 01:44 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: ADS SQL Access Module problems

Hello All:

Kay Rozeboom and I are having difficulty getting an ADS dialog to access
an SQL access module. I'm sure my explanation will create more
questions,
but the gist is this:

ADS dialog with embedded SQL which can be executed successfully in OCF.
Compiled the dialog, the created the access module in the same schema
indicated in ADSC Database Specifications screen.

When the dialog is executed, it always returns an SQLSTATE=42503
(42=Syntax error.... 503=Authorization failure) and SQL error
message DB00552 1 T26018 C-4M321: Missing authorization for <access-
module name>.

What we can't figure out is why?

Thanks,

Tim Gortner
State of Iowa
Department of Human Services
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: ADS SQL Access Module problems
"Tim,

It has been a while since we did this but we also created an access
module entity via OCF for our dialog. Here is the syntax, I'm certain
someone at CA walked us through this part.

CREATE ACCESS MODULE FISSQL1T.PC01C10D VERSION 1
FROM APPLDICT.PC01C10D
AUTO RECREATE ON
VALIDATE ALL
READ WRITE
DEFAULT ISOLATION CURSOR STABILITY
;

The access module name is schema.dialog in the CREATE statement. Hope
this help you some.


Joe S Cates, Database Analyst II
Information and Organizational Systems
Database Management/Unix Administration
Montgomery County Public Schools
Rockville, MD 20850
301-279-3697
joe_cates@mcpsmd.org

Outcomes