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

[ca.portal.admin]

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
AREA/RECORD Dependency Report
"Hello Joe:

You do not have to remove the DD Statements and make the job abort, most
IDMS shops now use dynamic allocation so that would not work, but, the UNLOAD
job step is strictly retrieval only.

I do the same thing that you do, but, once the report is created I cancel
the Unload job.

Bill Allen

In a message dated 5/9/2005 4:33:00 P.M. Eastern Daylight Time,
[e-mail] writes:

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: RHDCSRTT decompile utility
"What you need to do is to decompile the message using an older release.

From: Bill Allen <[e-mail]>
Reply-To: IDMS Public Discussion Forum <[e-mail]>
To: [e-mail]
Subject: Re: RHDCSRTT decompile utility
Date: Mon, 9 May 2005 13:13:28 EDT

In a message dated 5/9/2005 11:40:24 A.M. Eastern Daylight Time,
[e-mail] writes:

QW55b25lIHRoYXQgaGFzIHRoZSBEQyBDT0JPTCBwcm9ncmFtIHRoYXQgSSB3cm90ZSB0byBkZWNv
bXBpbGUgdGhlIFJIRENTUlRUIGxvYWQgbW9kdWxlIHNob3VsZCBOT1QgdXNlIGl0IHVuZGVyIHJl
bGVhc2UgMTYuIEJlc2lkZXMgbm90IGdlbmVyYXRpbmcgdGhlIGNvcnJlY3Qgb3V0cHV0LCBJdCBh
cHBlYXJzIHRvIGdvIGludG8gYSBDUFUgbG9vcC4NCiANCkknbGwgc2VuZCBhIG1lc3NhZ2Ugd2hl
biBJIGZpeCBpdC4gDQogDQpUaGFua3MsIFBhdWwgTWNSb2JlcnRzIA0KDQoJIA0KDQo=



This is what I received?????

"
IDMS Public Discussion Forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Mixed page group
"Hot off the press:
JCL:
//PCHPG JOB (DBA),CLASS=A,MSGCLASS=X,RESTART=HERE
//*-----------------------------------------------------------------
//* EXTRACT AREAS WITHIN PAGE GROUP FOR SPECIAL SSC
//*-----------------------------------------------------------------
//EXTAREA EXEC CULPPM,CV=IDMSQA
//SYSPCH DD DSN=IDMSQA.DBA.SRC(OPERDBAR),DISP=SHR
//SYSIN DD *
DATABASE DICTNAME=SYSDIRL DBNAME=AEIDICT
PARAM=NOLIST
USE PCHPGRPA CH R TO 1
SEL DMCL-1035 WHEN NAME-1035 = 'AEIDMCL' $ GLOBALDMCL
SEL AREA-1026 WHEN SEGMENT-1026 = 'OPERDB' $ EITHER SEGMENT NAME
$SEL AREA-1026 WHEN PAGEGROUP-1026 = NNN $ OR PAGEGROUP
//SYSIDMS DD *
DMCL=AEIDMCL,ECHO=ON
//HERE EXEC PGM=IEFBR14
//PCHSS EXEC CULPPM,CV=IDMSQA
//AREAS DD DSN=IDMSQA.DBA.SRC(OPERDBAR),DISP=SHR INPUT
//SYSPCH DD DSN=IDMSQA.DBA.SRC(PG$SSC),DISP=SHR OUTPUT
//SYSIN DD *
DATABASE DICTNAME=SYSDIRL DBNAME=AEIDICT
PARAM=NOLIST
USE PCHSSSYN WITH VAL ('MASTERDB') CH R TO 2 $ (SCHEMA NAME)
//SYSIDMS DD *
DMCL=AEIDMCL,ECHO=ON
//*
---------------------------------------------------------------
Culprit Syntax PCHPGRPA
01$ -------------------------------------------------------------
01$ PUNCH AREA W/IN PG-GRP/SEGMENT
01$ -------------------------------------------------------------
IN 2000 DB SS=IDMSNWKG,IDMSNTWK,1
PATHPG DMCL-1035 DMCLSEGMENT-1038 SEGMENT-1047 AREA-1026
01OUT D CARD
01SORT NAME-1026
01510001 SEGMENT-1026
01510009 NAME-1026
01510042 PAGEGROUP-1026 FM '9999'
017 IF PATH-ID NE 'PG' DROP
---------------------------------------------------------------------
Culprit Syntax PCHSSSYN
IN 2000 DB SS=IDMSNWKA,IDMSNTWK
PATHAR SA-018
PATHRC SA-018 SAM-056
PATHSS SA-018 SAM-056 SRCD-113 SOR-046
SEL SA-018 WHEN S-NAME-018 = '&&1' $ SCHEMA NAME
KEY 80 F PS KF=10,32 DD=AREAS
01OUT D CARD
01SORT TYP INIT
010 TYP ' '
010 INIT ' '
01410001 'ADD SUBSCHEMA XXXXXXX OF SCHEMA &&1 .'
01510001 'ADD AREA'
01510011 SA-NAM-018
01510043 '.'
01510079 TYP
01510080 INIT
01520001 'ADD REC '
01520011 SR-NAM-056
01520043 '.'
01520079 TYP
01520080 INIT
01530001 'ADD SET '
01530011 SET-NAM-046
01530043 '.'
01530079 TYP
01530080 INIT
01540001 'GENERATE.'
017 EOF = 200
017 IF PATH-ID = 'AR' 010
017 IF PATH-ID = 'RC' 020
017 IF PATH-ID = 'SS' 030
017 DROP
017010M 'A' TYP
017 M SA-NAM-018 INIT
017 TAKE ( 1 )
017020IF SR-NAM-056 = 'SR7' DROP
017 M 'R' TYP
017 M SR-NAM-056 INIT
017 TAKE ( 2 )
017030IF SR-NAM-056 = 'SR7' DROP
017 IF S-NAME-113 NE S-NAME-018 DROP
017 IF SOR-ID-046 NE SR-ID-113 DROP
017 M 'S' TYP
017 M SET-NAM-046 INIT
017 TAKE ( 3 )
017200M '9' TYP
017 TAKE ( 4 )

* NO warranty given or implied
* DYODD
* DHL takes no responsibility for use of this software
* etc, etc, etc.