ca.portal.admin

Re: System Index area expansion

Discussion created by ca.portal.admin on Sep 5, 2007
Hi Martin,

Thks for the info. Just wonder why the performance of the application
was
not affected before the index area expansion. We did not change any
schema
or segment definition.

Thks

Rgds



Martin Wieland
<martin.wieland@NE To:
IDMS-L@LISTSERV.IUASSN.COM
CKNET.COM> cc:
Subject: Re: System Index
area expansion

Sent by: IDMS
Public Discussion
Forum
<IDMS-L@LISTSERV.I
UASSN.COM>


04/09/2007 07:00
PM
Please respond to
IDMS Public
Discussion Forum





Hi Lim,
Did you specify a page reserve of approx. 29% in the index area
definition? This allows for the index to grow without using too much
overflow pages. Also make sure that you have done your maths concerning
the index block contains (IBC) and page offset values in conjunction
with the page size and the number of pages in the area. Just increasing
the page range by itself is in general not sufficient. The index will
have plenty of space to grow, but this space will not be used
efficiently and you will end up with SR8's scattered all over you area.
Note that you can specify the IBC and pageoffset in the DMCL (segment
defintion) using a symbolic key that must match the same key in the
schema. The Database Administration guide contains information on both
the page reserve and on how to calculate the IBC, page offset, number of
pages and pagesize. If you get them wrong the insert performance will
suffer, especially if it's the first large insert job after the
expansion. In addition you could take a look at some reports that tell
you about the index' structure (IDMSDBAN, PRINT INDEX, etc.). Indexes
that have a high upgrade factor (many insert and deletes) are candidates
for regular maintenance using the REBUILD INDEX utility.

Good luck,
Martin Wieland
Neckermann.com



-----Oorspronkelijk bericht-----
Van: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
Namens Woo Liew
Verzonden: dinsdag 4 september 2007 12:39
Aan: IDMS-L@LISTSERV.IUASSN.COM
Onderwerp: System Index area expansion


Hi,

Recently, we had done a system index area expansion. We unloaded the
index
data, increased the page range of the area and reloaded back the data to
the area. The occurrences of the SR8 were reduced significantly from
about
60k to about 20k. However, when the application programmer run their
routine job to store the data into the related record area ( member of
the
index set), it experienced significant slowness. The job took about
45min
to 1 hour to store the same amount of data (about 150k) before the
expansion and took about 10 hours after the index expansion. The number
of
SR8 increased from 20k to 40k after the completion of the job.

This was the first time we did an index area expansion. We are not so
sure
what has gone wrong and what is the cause of the slowness after the
expansion.

We need the expert's advice on this.

Thks in advance

Rgds


Lim


WARNING: This communication is meant only for the addressee(s) named
above and may contain information which is confidential and/or legally
privileged. If you are not the named addressee(s), or the agent
responsible for receiving and delivering this communication to the named
addressee(s), this communication has been sent to you in error. If so,
kindly notify the sender and delete the information immediately.
Unauthorised dissemination, distribution, copying or reliance on this
communication is prohibited and may attract criminal penalties.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: System Index area expansion
"Hi Martin,

Thks for the info. Just wonder why the performance of the application was
not affected before the index area expansion. We did not change any schema
or segment definition.

Thks

Rgds



Martin Wieland
<martin.wieland@NE To: IDMS-L@LISTSERV.IUASSN.COM
CKNET.COM> cc:
Subject: Re: System Index area expansion

Sent by: IDMS
Public Discussion
Forum
<IDMS-L@LISTSERV.I
UASSN.COM>


04/09/2007 07:00
PM
Please respond to
IDMS Public
Discussion Forum





Hi Lim,
Did you specify a page reserve of approx. 29% in the index area
definition? This allows for the index to grow without using too much
overflow pages. Also make sure that you have done your maths concerning
the index block contains (IBC) and page offset values in conjunction
with the page size and the number of pages in the area. Just increasing
the page range by itself is in general not sufficient. The index will
have plenty of space to grow, but this space will not be used
efficiently and you will end up with SR8's scattered all over you area.
Note that you can specify the IBC and pageoffset in the DMCL (segment
defintion) using a symbolic key that must match the same key in the
schema. The Database Administration guide contains information on both
the page reserve and on how to calculate the IBC, page offset, number of
pages and pagesize. If you get them wrong the insert performance will
suffer, especially if it's the first large insert job after the
expansion. In addition you could take a look at some reports that tell
you about the index' structure (IDMSDBAN, PRINT INDEX, etc.). Indexes
that have a high upgrade factor (many insert and deletes) are candidates
for regular maintenance using the REBUILD INDEX utility.

Good luck,
Martin Wieland
Neckermann.com



-----Oorspronkelijk bericht-----
Van: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
Namens Woo Liew
Verzonden: dinsdag 4 september 2007 12:39
Aan: IDMS-L@LISTSERV.IUASSN.COM
Onderwerp: System Index area expansion


Hi,

Recently, we had done a system index area expansion. We unloaded the
index
data, increased the page range of the area and reloaded back the data to
the area. The occurrences of the SR8 were reduced significantly from
about
60k to about 20k. However, when the application programmer run their
routine job to store the data into the related record area ( member of
the
index set), it experienced significant slowness. The job took about
45min
to 1 hour to store the same amount of data (about 150k) before the
expansion and took about 10 hours after the index expansion. The number
of
SR8 increased from 20k to 40k after the completion of the job.

This was the first time we did an index area expansion. We are not so
sure
what has gone wrong and what is the cause of the slowness after the
expansion.

We need the expert's advice on this.

Thks in advance

Rgds


Lim


WARNING: This communication is meant only for the addressee(s) named
above and may contain information which is confidential and/or legally
privileged. If you are not the named addressee(s), or the agent
responsible for receiving and delivering this communication to the named
addressee(s), this communication has been sent to you in error. If so,
kindly notify the sender and delete the information immediately.
Unauthorised dissemination, distribution, copying or reliance on this
communication is prohibited and may attract criminal penalties.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Data Encryption in IDMS
"Does anyone know of a third-party product that can be used to encrypt
sensitive data in an IDMS database?

TIA.

Arnie Isaac


--------------------------------------------------
This e-mail and any files transmitted with it may contain privileged or confidential information.
It is solely for use by the individual for whom it is intended, even if addressed incorrectly.
If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute,
or take any action in reliance on the contents of this information; and delete it from
your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.
--------------------------------------------------
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS on VSE and MQSeries
"Hi Shelley:

I remember that we test something on VSE but I'm not shure if OCA-MQ work on VSE, I beleive yes, you can check here:

http://www.datadirect.com/products/mainframe-integration/other-products/idms/oca-mq/index.ssp

We are using OCA-MQ on Z/OS and its working very good, we have full implemented with a lot of sync/async communications and a lot of triggers. Check if the product works for VSE, any other question just let me know.

Thasnks.

J. Sotela> Date: Thu, 6 Sep 2007 12:01:38 -0400> From: shelley.fandrey@CGI.COM> Subject: IDMS on VSE and MQSeries> To: IDMS-L@LISTSERV.IUASSN.COM> > > > We are running IDMS/DC 15.0 on z/VSE and starting to look at being part> of an MQSeries ""collective"". Has anyone done this with IDMS on VSE? > > > > We've asked CA and their suggestions (since we are VSE and not z/OS and> they know of no third party products for VSE to help) were to either put> in a CICS frontend for IDMS to run the MQSeries software, or to put in> IDMS Server and the SQL Option to talk to Websphere MQ.> > > > Thanks in advance. > > > > Shelley Fandrey
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS on VSE and MQSeries
"We are running OCA-MQSERIES for IDMS release 16.0 SP4 on z/OS 1.6 (we
ran it on 15.0 SP4 also). I don't know if the support VSE but the web
site is
http://www.neonsys.com/support

We use OCA-MQSERIES for IDMS to connect to the mainframe Queue Manager
which talks to Unix and Windows servers.

Steve Harmeson

Outcomes