ca.portal.admin

ERROR DB006001in BCF doing UNLOCK SEGMENT

Discussion created by ca.portal.admin on Feb 7, 2008
Latest reply on Feb 8, 2008 by ca.portal.admin
Hello All:

I am trying to do an unlock segment in IDMSBCF release 15.0 SP6 and we
get
error DB006001 trying to unlock a segment with a special character in
the
name, for example the segment name is @CCS.

We tried no quotes, single quotes and double quotes, nothing works.

However, it does work when we do an individual area name with double
quotes
around the identifier? So we do have a get around but this segment has
hundreds of areas.

Has anyone else experienced this issue and know of an APAR?

I searched support connect and found one issue for 16.0 only and it was
not
for the UNLOCK SEGMENT command.

Thanks in advance for your support.

Bill Allen
(704) 641-0296

@ccs



**************Biggest Grammy Award surprises of all time on AOL Music.
(http://music.aol.com/grammys/pictures/never-won-a-grammy?NCID=aolcmp003
000000025
48)
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: QSAM or PREFETCH - pros and cons
"I did benchmark tests of IDMSQSAM vs. PREFETCH for two programs that did
area sweeps a couple of years ago.
I ran each program 5 times each way and then averaged the results.

I was surprised to see IDMSQSAM as the hands-down winner.
However, IDMSQSAM used more CPU..... I think about 10 - 15 % more.

Thanks.
Jon Gocher



----- Original Message -----
From: ""Petzold, Lutz"" <PetzoldL@AETNA.COM>
To: <IDMS-L@LISTSERV.IUASSN.COM>
Sent: Thursday, February 07, 2008 11:14 AM
Subject: Re: QSAM or PREFETCH - pros and cons


As these comments indicate, not all IO is the same. Fastaccess and
QSAM's fame to claim is that they do not do block io. Fastaccess does
either track IO or cylinder IO. Meaning, one IO request and a whole
cylinder's worth of data ends up in the buffer. Additionally,
Fastaccess allows for large buffer allocations. One caveat though,
these buffers are searched sequentially for data. That is not the most
efficient. IDMS searches its buffers through an algorithm, resulting in
less CPU. What kind of IO QSAM does I dont know, I just know it's so
lightening fast, that it took me more time proving the program actually
updated all the data then writing the thing in the first place.
However, due to its limitations, I've never used QSAM for production
batch jobs. Fastaccess I have, and the full cylinder read feature does
save a ton of time. Searching through large buffers for data, only to
find it isn't there and a full cylinder IO is required, burns CPU. And,
full cylinder io does take more milliseconds (or are they down to
nannoseconds now?) then one block io, so if your app only uses one page
of the cylinder's worth of pages, your performance will actually
decrease. Comparing Fastaccess performance to prefetch has always shown
me, and the people that i worked with, that fastaccess is faster if
applied judiciously. But reading the statistics, understanding the
access path, and coming up with the right parms, can be a head trip. I
happened to work with the unofficial guru of Fastacess at one time, and
he made sure that every dba understood the product. It can get
complicated, especially with indexes, and cross area sets and mixed mode
(sequential and random) acess.

The bottom line with Fastaccess is, the dba has to know what the dba is
doing, or it can hurt.


Lutz Petzold
TDM UDB/IDMS Support
(401) 782 2265 or (860) 636 0291
Pager (860) 366 0865 or Telalert



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
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: ERROR DB006001in BCF doing UNLOCK SEGMENT
"I suppose one could write a ... CULPRIT ... to walk the SEGMENT-1047
-> AREA-1026 and build the unlock syntax

in fact - if you wait until tomorrow - i will throw one rogether




At 05:37 PM 2/7/2008, you wrote:
Hello All:

I am trying to do an unlock segment in IDMSBCF release 15.0 SP6 and we get
error DB006001 trying to unlock a segment with a special character in the
name, for example the segment name is @CCS.

We tried no quotes, single quotes and double quotes, nothing works.

However, it does work when we do an individual area name with double quotes
around the identifier? So we do have a get around but this segment has
hundreds of areas.

Has anyone else experienced this issue and know of an APAR?

I searched support connect and found one issue for 16.0 only and it was not
for the UNLOCK SEGMENT command.

Thanks in advance for your support.

Bill Allen
(704) 641-0296

@ccs



**************Biggest Grammy Award surprises of all time on AOL Music.
(http://music.aol.com/grammys/pictures/never-won-a-grammy?NCID=aolcmp003000000025
48)
This is Chris Hoelscher and I approved this email
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"FW: IDMS Indexing: Learn from the experts, join our live webcast!"
"A message from CA.......


CA <http://www.ca.com/>

Webcast on
Mainframe<http://www.ca.com/images/email/mf_webcast_header.jpg>

<http://www.ca.com/images/email/dot.gif>


14 & 21 February 2008


Webcast on Maintaining CA IDMS(tm) Indexes


Dear CA IDMS user,

Please join us for a two-part webcast series on Maintaining CA
IDMS(tm)/DB Indexes. In today's 24x7 economy it is of the utmost
importance that you get optimal database performance for your mission
critical business systems is. In working with some of the largest IDMS
clients around the world, our technical staff has developed a number of
Best Practices that we would like to share with you. You will be given
insight into the internal workings of IDMS and learn some of the latest
indexing techniques. We look forward to welcoming you on 14 February and
21 February!

The CA IDMS Development Team

CA IDMS(tm)/DB Indexing, Part 1 of 2: Internals
Join us for Part 1 of our series on CA IDMS(tm)/DB indexing.

<http://www.ca.com/images/email/chevron_single.gif>

14 Feb 2008 11:00 a.m. EST
<http://ca.com/us/events/item.aspx?e=163609&eis=1>



CA IDMS(tm)/DB Indexing, Part 2 of 2: Maintaining Indexes
Join us for Part 2 of our series on CA IDMS(tm)/DB indexing.

<http://www.ca.com/images/email/chevron_single.gif>

21 Feb 2008 11:00 a.m. EST
<http://ca.com/us/events/item.aspx?e=163608&eis=1>



>><http://www.ca.com/images/email/ext_email_cta_arrow1.gif>

More Information on this webcast series
<http://ca.com/us/events/list.aspx?e=467>

<http://www.ca.com/images/email/dot.gif>

<http://www.ca.com/images/email/dot.gif>

<http://www.ca.com/images/email/dot.gif>

CA, One CA Plaza, Islandia, NY 11749
This message is a solicitation from CA. To stop receiving such emails,
click here
<https://www.ca.com/us/register/opt.aspx?em=Jean.Rissmiller@CA.COM&act=e
mea_webcast_MUK_UK-Events_04february2008> .

Contact Us <http://www.ca.com/us/contact/> Legal Notice
<http://www.ca.com/us/legal/> Privacy <http://www.ca.com/us/privacy/>
ca.com <http://www.ca.com/>
Copyright (c) 2008 CA. All rights reserved.

<http://redirect.ca.com:8080/trk/open?ref=zo19sr69h_0-1c93x14>
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
VS-Cobol and Release 16?
"Hi Lister's:

Does anyone have experience running a VS-Cobol application under IDMS R16
SP5 or SP6?

I have a client planning a R15 to R16 upgrade, and they have a production
application running OS/VS Cobol as 'LE compliant' in R15, and they do not
want to migrate their Cobol environment at this time.

Any knowledge you're willing to share is greatly appreciated in advance!

Regards,

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








Normal

Normal
Re: VS-Cobol and Release 16?
"We still run our VM to MVS/IDMS cobol as VS/COBOL . . .
There is no issue particular to IDMS 16.0 of which we are aware.

DEM

Outcomes