ca.portal.admin

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: [IDMSVENDOR-L] Mixed page group
"To get the area dependencies for an unload/reload of an area I run the job without DD cards for the IDMS database files. This causes an abend and generates a list of the
dependent areas along with the sets and records in the area. I'm not sure if it shows you every set and record in the other areas or just those affected by the unload/reload.
Here's a sample of the output.

UNLOAD SEGMENT FISCHEMP USING FISSRESP
AREA ""FIS-AP-AREA""
RELOAD INTO FISCHEMP USING FISSRESP DMCL JSCDMCLP;
UT001002 UNLOAD WILL USE SS FISSRESP DMCL GLBLDMCP SEGMENT FISCHEMP
UT001003 RELOAD WILL USE SS FISSRESP DMCL JSCDMCLP SEGMENT FISCHEMP
UT003001 BINDING SUBSCHEMA FISSRESP TO DMCL GLBLDMCP USING DBNAME FISCHEMP
SUBSCHEMA NAME ------ FISSRESP
COMPILE DATE -------- 05-02-08
COMPILE TIME -------- 04.42.52
SUBSCHEMA VERSION --- 1200

IDMSUNL1 AREA RECORD DEPENDENCY TABLE FOLLOWS:
AREA-NAME SET-NAME RECORD-NAME:
FIS-ACCT-AREA FY-EOY-SET FISCAL-YEAR-REC - OWNER
FIS-ACCT-AREA ACCT-PO-SET FY-FUND-BAL-REC - OWNER
FIS-ACCT-AREA ACCT-SHIPLST-SET FY-FUND-BAL-REC - OWNER
FIS-ACCT-AREA FIS-DETAILS-SET FY-FUND-BAL-REC - OWNER
FIS-ACCT-AREA FIS-OFFSET-SET FY-FUND-BAL-REC - OWNER
FIS-ACCT-AREA FUND-PAY-ADJ-SET FY-FUND-BAL-REC - OWNER
FIS-ACCT-AREA FY-FUND-DET-SET FY-FUND-BAL-REC - OWNER
FIS-AR-CR-AREA FIS-DETAILS-SET AR-CR-DETAIL-REC - MEMBER
FIS-AR-CR-AREA FIS-OFFSET-SET AR-GENER-INT-REC - MEMBER
FIS-CHECK-AREA CHECK-PAY-AD-SET CHECK-NUMBER-REC - OWNER
FIS-CHECK-AREA CHECK-WRITE-SET CHECK-OOAK-REC - OWNER
FIS-CHECK-AREA EMP-TRANS-NO-SET EMPLOYEE-SSN-REC - OWNER
FIS-CHECK-AREA VEND-PAY-AD-SET VEND-INV-NO-REC - OWNER
FIS-CHECK-AREA VEND-TRAN-NO-SET VENDOR-NAME-REC - OWNER
FIS-CHECK-AREA VENDOR-PAY-SET VENDOR-NAME-REC - OWNER
FIS-INVOICE-AREA AP-AR-SET INVOICE-LINE-REC - OWNER
FIS-LOCA-AREA LOC-SHIPLST-SET LOCATION-NO-REC - OWNER
FIS-LOCA-AREA LOC-TRANS-NO-SET LOCATION-NO-REC - OWNER
FIS-LOCA-AREA OUTSTAND-PO-SET LOCATION-NO-REC - OWNER
FIS-LOCA-AREA LOC-PCARD-SET LOCATION-NO-REC - OWNER
FIS-OTHER-AREA FIS-OFFSET-SET OT-GENER-INT-REC - MEMBER
FIS-OTHER-AREA FIS-DETAILS-SET OTHER-DETAIL-REC - MEMBER
FIS-TABLE-AREA DATE-PAY-ADJ-SET FIS-DATE-REC - OWNER
FIS-TABLE-AREA UTILITY-PAY-SET UTILITY-ID-REC - OWNER
MM-CATALOG-AREA PO-PRINT-SET MMS-OOAK-REC - OWNER
MM-CATALOG-AREA PO-REPRINT-SET MMS-OOAK-REC - OWNER
MM-INVOICE-AREA TRANS-ITEM-SET CONSLD-ITEM-REC - MEMBER
MM-INVOICE-AREA PAY-ADJ-ITM-SET INV-LINE-ITM-REC - OWNER
MM-LOC-ACCT-AREA CCTR-SHIPLST-SET COST-CENTER-REC - OWNER
MM-LOC-ACCT-AREA COSTCTR-PO-SET COST-CENTER-REC - OWNER

UT004001 IDMSDBL1 RELEASE 15.0 TAPE CAGJF0 PROCESSING STARTED
SUBSCHEMA NAME ------ FISSRESP
COMPILE DATE -------- 05-02-08
COMPILE TIME -------- 04.42.52
SUBSCHEMA VERSION --- 1200





IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM> writes:
So...does anyone have an automated way to get a list of all the records,
sets, and areas in a segment? (To build the special subschema for the
unload/reload.)


-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Linda Campbell
Sent: Monday, May 09, 2005 1:33 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: [IDMSVENDOR-L] Mixed page group

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
Joe S Cates, C.C.P.
Database Analyst
Office of Global Access Technology
Montgomery County Public Schools
Rockville, MD 20850
email: Joe_Cates@fc.mcps.k12.md.us

"
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
"We have a global subschema as well. I am actually asking for the
opposite - a subschema that contains only entities located in a specific
segment (or page group). The problem is that the segment/page group
information is not contained in the schema, only in the DMCL.

Outcomes