ca.portal.admin

ACCEPT DML VERB in COBOL not working

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



I am trying to get the system version by issuing an accept sysversion
and it is NOT working.



Here is the code: ACCEPT SYSVERSION INTO WS-TEST1.



Here is the Working Storage area: 01 WS-TEST1
PIC
S9(4) COMP.



The accept DML verb is issued immediately after the bind run unit, bind
records and ready of the areas.



What we get is 0000, the system version number that we should get is 33.



Here is the enter next task code prompt: V33 ENTER NEXT TASK CODE:
CA-IDMS release 16.0 node SYST0033



We are running 16.0 SP2 on a Z/OS 1.7 Operating System.



Any help would be appreciated.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Orphans in unlinked indexes?
"Rozeboom, Kay [DAS] wrote:
We have heard many times that we don't need to be concerned about orphans for unlinked indexes (INDEX DBKEY POSITION IS OMITTED). But when I do index prints for busy unlinked indexes, I see orphans galore at the L1 level. Are these real orphans? Should we be concerned?

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



Kay

I became somewhat disenchanted when I learned this (the hard way).
While unlinked indexes do not get orphans on the bottom level, they
still form on the upper levels.

To add insult to injury, the TUNE INDEX function function of BCF/OCF
ONLY works on bottom level SR8s - it does not adopt orphans on the upper
levels. I have heard from CA that this is supposed to be resolved under
release 17.

Jim Ritterbusch
GE Capital Solutions
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: ACCEPT DML VERB in COBOL not working
"Hi Bill:

I think Bob is right, although I have been able to get SYSVERSION to work
using an ADS Dialog with an ACCEPT DML verb running under IDMSBCF in CV mode
(the same ADS dialog running in local mode returns a SYSVERSION = 0, which
is not unexpected).

I know I've tried this, but it's been a while and I don't recall whether I
got SYSVERSION to work in Cobol or not...The Cobol ACCEPT is a bit odd, in
that it only runs in CV mode (you'll get a lovely vector abend if you
execute a Cobol ACCEPT in local mode). Since the documentation does not
necessarily imply that SYSVERSION is 'only for online', I might argue that
SYSVERSION is a reasonable request whether the protocol is DC or DC Batch.
Just my 2cents...That said, there are other ways of getting the CV version
number...

Regards,

Tom Schoenborn

----- Original Message -----
From: ""Bob Wiklund"" <wiklund@TIBURONTECH.COM>
To: <IDMS-L@LISTSERV.IUASSN.COM>
Sent: Friday, June 06, 2008 4:00 PM
Subject: Re: ACCEPT DML VERB in COBOL not working


Bill,

I believe that what you're trying to do is only valid for an online program.
In the DML manual, the Accept SYSVERSION command implies an online program.

Bob Wiklund
Tiburon Technologies
623 594-6022

Bob Wiklund
Tiburon Technologies
623 594-6022

________________________________

From: IDMS 3rd-party providers forum on behalf of William M. Allen, Jr.
Sent: Fri 6/6/2008 2:39 PM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject: Re: ACCEPT DML VERB in COBOL not working



Hello Terry:

They are trying to do this from a batch COBOL program.

Sorry, I missed providing that information; here is the IDMS-CONTROL:

002500 IDMS-CONTROL SECTION.
002600 PROTOCOL. MODE IS BATCH DEBUG
002700 IDMS-RECORDS MANUAL.

William M. Allen, Jr.
ARCH Consulting Associates, Ltd.
(704) 641-0296

Outcomes