ca.portal.admin

Re:Re: [IDMSVENDOR-L] Mixed page group

Discussion created by ca.portal.admin on May 9, 2005
Close, but no cigar Chris. We do not have any sets that cross page
group boundaries. We do however have areas with the same page ranges in
multiple page groups. That is where we have had problems.



Here is the response I got from CA when I asked SPECIFICALLY if you can
use a mixed page group subschema with UNLOAD after we experienced a
failure in RELOAD. I guess no one got the docup:







SEE THE FOLLOWING SOLUTION(S):

IDMS 15.0 T 303

*
________________________________________________________________________
____
*



* ID: 303

* PRODUCT: IDMS

* RELEASE: 15.0

* DESC: TCC TEST PTF

* SOLUTION TYPE: TEST

* SYSTEMS AFFECTED: OS

* SOLUTION TEXT:



**********************************************************************

* PROB #: IDMS 2734 PDC: BC03048 DATE: 31 DEC 2003 *

* *

* ***** Product Documentation Change ***** *

* *

* PROBLEM DESCRIPTION: The CA-IDMS Utilities manual is unclear as to *

* what is meant when it states that the UNLOAD *

* cannot process multiple page groups. *

* *

**********************************************************************







PROBLEM RESOLUTION:



The description of the inability to use the UNLOAD utility with multiple
page groups in Section 4.30.2 of the CA-IDMS Utilities manual needs a
clarification.



Replace the Mixed Page Group paragraph in Section 4.30.2 (Unload
utility) of the CA-IDMS Utilities manual with the following text.



USING UNLOAD and MIXED PAGE GROUPS: UNLOAD cannot process mixed page
groups. The subschemas specified for use by the UNLOAD utility cannot
contain areas that reside in a page group other than the page group for
the segment being unloaded.



If the environment has an EXIT34 installed that exit will be invoked.

If the CA supplied EXIT34 is used (RHDCUX34) and has not been altered a
message will be produced indicating that an unqualified FIND/OBTAIN
DBKEY command has been issued. If the exit has been modified to abort
the associated run-unit when this type of command is encountered the
UNLOAD utility will be abnormally terminated. You must us multiple
invocations of the utility to process areas in different page groups.







*
________________________________________________________________________
____
*



* OS VERSION: 0 UNCONFIRMED

*** NO ZAPS FOR THIS VERSION ***






************************************************************************
****

+++ Subscribe Now To CA's E-News Technical Newsletter +++

For Information Visit Us At: http://eSupport.ca.com

==> Come Visit CA's Open Forum at: http://forums.ca.com <==


************************************************************************
****





*** Contact technical support Monday - Friday 8:30AM - 7:00 PM EST

*** CA-IDMS/DB 856 273 3411 CA-IDMS/DC 856 273 3410

CA-IDMS/ADS 856 273 3414 CA/IDMS/TOOLs 856 273 3417

STARTCC - 856 273 3412 eSupport 631 342 6364

************************************************************************
****
**



END OF STARTRAK MESSAGE

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








Normal

Normal
Re: Order of members in an unsorted via set
"Hi Richard,

It's implied in the responses you got back, but I thought I would restate
things just in case you missed it. The ORDER clause of the SET statement
determines how records are stored in relation to the current of set. For
example, if ORDER IS NEXT is used, and a member of the set is current of
set, then the new record will be stored immediately after the member
record, no matter where that record is in the set. As others have said, if
the owner record is current of set, then the new member record will be
stored at the head of the set. If a member record in the middle of the set
is current, then the new record will be added to the middle of the set.
The only way new records will get stored to the end of the set is if the
last member record in the set is current of set. It sounds like what you
really wanted for this set is ORDER IS LAST, which would always store new
records at the end of the set. Usually the only time you would use ORDER
IS NEXT is when you don't care where the record ends up in the set, or if
you control where the record is stored through program logic (i.e.,
walking the set to find the insertion point, and then storing the new
record).

Hope this clears things up.

Dave Slocum
Consumers Energy

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








Normal

Normal
Imre Koenders/CB/Achmea is op cursus
"Ik ben niet op kantoor vanaf 05/12/2005 tot 01/31/2010.

Geachte iedereen.

Vanaf 1 juni 2005 ben ik buiten achmea active werkzaam.

Voor vragen over sql server:
Ton Leer (053)484 6511
Gerard Oosterik (053)484 6449

Vragen over idms:
Edwin Schoeman (055)579 3156
Paul van Vuren (055)579 5139

overig:
imre mobiel 06-55733719

Prettig met jullie kennisgemaakt te hebben. Ik wens jullie allen het
allerbeste.

m.v.g.

imre



********************* DISCLAIMER *********************
De informatie in dit e-mail bericht is uitsluitend
bestemd voor de geadresseerde. Verstrekking aan
en gebruik door anderen is niet toegestaan.
Door de electronische verzending van het bericht
kunnen er geen rechten worden ontleend aan de
informatie.
************************************************************

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








Normal

Normal
Re: [IDMSVENDOR-L] Mixed page group
"Thanks for letting me know. . .
Glad to be of help. . .
dem

Outcomes