ca.portal.admin

Re: CA-1 and Unload/Reload

Discussion created by ca.portal.admin on Jan 2, 2007
Hello All:

Thank you Chris Hoelscher, this confirms the information that I found
on
Google, and that it actually works using temporary data set names.

Has anyone used the new features of 'Express REORG' from IDMS 16.0 SP4
yet?

From what I read it seems like this might eliminate the need for
stepped
reloads and greatly speed up the process for larger unloads and
reloads?

Bill Allen

In a message dated 1/2/2007 8:53:52 A.M. Eastern Standard Time,
choelscher@HUMANA.COM writes:

sorry to jump in late on this one .. i definitely have had this problem
in
the past, and we circumvented as follows: (relevant JCL for reload)

//SYS001 DD DSN=IDMS.UNLOAD.SYSPCH,DISP=SHR
//SYS002 DD DSN=IDMS.UNLOAD.SYS002(0),DISP=SHR
//SYS003 DD DSN=IDMS.UNLOAD.SYS003(0),DISP=SHR
//SYS005 DD DSN=&&DBL005,DISP=(NEW,PASS),UNIT=(TAPE,,DEFER),
// VOL=(,,,35),
// DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760)
//SYS006 DD DSN=&&DBL006,DISP=(NEW,PASS),UNIT=(TAPE,,DEFER),
// VOL=(,,,35),
// DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760)
//SYSPCH DD DSN=&&SORTRELD,DISP=(NEW,PASS),UNIT=3390,
// SPACE=(TRK,1),DCB=BLKSIZE=80
//RELDCTL DD DSN=IDMS.UNLOAD.RELDCTL,DISP=SHR

and the parms for the reload are:

RELOAD NOTIFY 100000 AS SORTEXIT REUSE WORKFILES;

Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com (mailTo:choelscher@humana.com)
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Dictionary Migrator message
"I get this message from the migrator:

ENTITY-NAME VERSION ERROR MESSAGE
C474M762 1 VALD231W- OPTIONS DIFFERENT
CATCH ALL

Here is the definition of the message:

VALD231W - OPTIONS DIFFERENT options list:

Reason: The table named has different characteristics in the source and
object dictionaries. The characteristics cannot be changed in a MODIFY
command, therefore the update of the table is complete unless remedial
action is taken first.

Action: Determine which characteristics should be used and correct the
appropriate entity.


This is the ""OBJECT"" table:

ADD
TABLE NAME IS C474M762 VERSION IS 1
PUBLIC ACCESS IS ALLOWED FOR ALL
TYPE IS CODE
SEARCH IS LINEAR
ENCODE DATA IS ALPHANUMERIC
DECODE DATA IS ALPHANUMERIC
TABLE IS UNSORTED
VALUES ARE ( ' ' ' ' '' '' TD06 1 MANU 2 )
*+       INCLUDE MAP M474M762 VERSION IS 1
*+           TYPE IS LINKED EDIT/CODE
GENERATE
.

This is the ""SOURCE"" table:

ADD
TABLE NAME IS C474M762 VERSION IS 1
PUBLIC ACCESS IS ALLOWED FOR ALL
TYPE IS CODE
SEARCH IS LINEAR
ENCODE DATA IS ALPHANUMERIC
DECODE DATA IS ALPHANUMERIC
TABLE IS UNSORTED
VALUES ARE ( ' ' ' ' '' '' TD06 1 MANU 2 PREV 3 )
*+       INCLUDE MAP M474M762 VERSION IS 1
*+           TYPE IS LINKED EDIT/CODE
GENERATE
.

Please note there is a change the table values and granted, it's a
warning message, but I cannot understand what the message means. Any
ideas?

Tim Gortner
State of Iowa
Department of Human Services
"
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] Dictionary Migrator message
"a linked table is one where the load module of the edit/code table is
stored IN the map load module, as opposed to an unlinked - where the table
load module is called in at runtime

my guess is .. because it is a LINKED table (as opposed to unlinked) - you
would have to un-associate the table from the map field - migrate the
table - and then re-associate the linked table with the map field - or at
least re-generate the (unchanged) map

your migrator SHOULD be doing this for you, but maybe not

of - make the tables UNLINKED and all this would most likely go away ...

Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com




The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Dictionary Migrator message
"I got a similar error (VALD206W - ELEMENT OVERRIDE IN RECORD) years ago
on a record element. CA sent me the following explanation for the
warning.

This warning message results when validating entities in the Extract
files against similar entities in the target dictionary. Here an
element's inherent description differs from the elements overrides
description in the record. Dicmig navigates the INQ-SDR set to access
the SR-036 ( record defn ) and then compares the SDR-042 with the
INQ-058 ( element defn ) for equality in the following fields : USE-042
, VAL-SW-042 , SIGN-042 , SEPERATE-042 , PIC-LGTH-042 against the same
named -058 fields. If any of these are unequal then the message will be
issued.

The base element and record element looked the same based on a DISPLAY
of each, but it turned out that fields that are not included in DISPLAY
output (VAL-SW-042 and VAL-SW-058) did not match.

Outcomes