II07902: IDCAMS EXPORT IMPORT - HINTS AND TIPS, USAGE AND DIAGNOSIS. VSAMINFO : CATRECOVERY CATALOG BROKEN REPRO

APAR status

• Closed as canceled.

Error description

• This APAR is intended to provide information to assist the user
  with the EXPORT and IMPORT process when used for the restoring
  and moving of ICF catalogs.  This is a supplement, but NOT a
  replacement, for the AMS Reference for Integrated Catalog
  Facility Guide (SC26490600) and/or the Managing Catalogs
  Guide (SC26491400).  Please refer to these manuals FIRST,
  before  using EXPORT and IMPORT cmds. They are invaluable for
  answering specifics on the various parameters, and provide
  numerous, actual sample jobs.  This information may be updated
  periodically, check the last update to determine the most
  current version.
  LAST UPDATE: 12/01/98  C. Coleman
  ** Subject List:
   1). How does EXPORT and IMPORT work?
   2). What's CONNECT and DISCONNECT?
   3). Before you start ....
   4). Shared catalog considerations.
   5). What to do if IMPORT or EXPORT fails.
   6). Common problems Q&A.
  ****************************************************************
  1). HOW DOES EXPORT and IMPORT WORK?
  EXPORT makes a portable copy of an ICF catalog.  The portable
  copy contains the catalog entries along with information on how
  the catalog was originally defined.  All of this information
  will be used to do the IMPORT later.
     EXPORT will also mark the catalog as having been EXPORTed.
  Beyond this indicator, EXPORT will not alter the catalog
  structure in any way.
  IMPORT restores a catalog by:
     a.  Opening the EXPORT portable data set to verify that it
         can be used.
     b.  DEFINing the new catalog.
     c.  DELETing the UCAT connector from the MASTER catalog.
     d.  COPY the data from the portable data set into the new
         catalog data sets.
     e.  DEFINing the new UCAT connector (and the ALIAS entries
         if the ALIAS parm was specified with the IMPORT).
     f.  DELETing the old catalog data sets.
  IMPORT will skip steps c and f if the user elects to DELETE the
  user catalog before starting the IMPORT, and it will also skip
  step (e) if the user pre-DEFINEs the new empty user catalog and
  specifies the INTOEMPTY parameter.
  NOTE: Do NOT use the EXPORT and IMPORT commands if you desire
        to change the name of the UCAT (rename).  If done so,
        MSGIDC3615I will be issued as the IMPORT function is
        terminated.  Instead, use the procedure that is noted
        in the Managing Catalogs guide : Renaming a Catalog.
        Wherein one first would define a new catalog, specifying
        the NEW catalog name, then, using AMS REPRO command,
        copy the original catalog asis, into the new catalog.
           This noted procedure is the ONLY valid method of
        renaming a catalog.
  ****************************************************************
  2). EXPORT DISCONNECT and IMPORT CONNECT versus
        EXPORT and  IMPORT :
  The EXPORT DISCONNECT and IMPORT CONNECT will only affect the
  UCAT connector and ALIAS records in the master catalog.
     IMPORT CONNECT will rebuild a UCAT connector record.
     EXPORT DISCONNECT will delete the UCAT connector and ALL of
  the ALIAS ENTRIES associated with it!! If the UCAT is associated
  with a NON SMS managed MCAT that is password protected, then
  user MUST supply the MASTERPW of this associated MCAT.  If
  this password is not coded on the IDCAMS EXPORT DISCONNECT
  ENTRY/NAME statement, then password prompt message MSGIEC301A
  will be issued at the operator console or a prompt for
  password will be sent to a TSO user console.  The AMS EXPORT
  DISCONNECT command does not use the password parm of the
  CATALOG statement.
     These commands are used most frequently in a shared catalog
  environment.  See the section on SHARED CATALOG CONSIDERATIONS.
  ****************************************************************
  3). Before you START, check your AMS and MANAGING CATALOG books:
   a.  Then run  DIAGNOSTICS  on the catalog that you are going
       to be working with BEFORE you start.  Any errors should be
       corrected first, because EXPORT and IMPORT will not verify
       any of the information being transferred. ICF is a VSAM
       KSDS.  Run the following AMS diagnostics :
              EXAMINE (INDEXTEST)
              EXAMINE (DATATEST)
              DIAGNOSE
              LISTCAT
       Common messages from EXAMINE include:
       MSGIDC11703I DUPLICATE KEYS IN INDEX
       MSGIDC11733I DATA COMPONENT KEY SEQUENCE ERROR
       MSGIDC11734I SEQUENCE SET & DATA CI KEY SEQ MISMATCH
       MSGIDC11741I DUPLICATE CONSECUTIVE KEYS FOUND
   b.  Run a  LISTCAT ENT(usercatname) CAT(usercatname) ALL  to
       get the original definition parameters and ALIAS names
       that are associated with the catalog.
   c.  Make sure you have the right RACF authority before you
       start, many problems can be avoided this way.  You will
       need ALTER to the user catalog, UPDATE to the master
       catalog.  If you EXPORT an active master catalog, you need
       ALTER to the master!
   d.  Use ALTER usercatname LOCK to lock the catalog prior to
       starting (including the shared systems!).  Remember to
       unlock the catalog on all of the systems when you are done.
   e.  Consider using DELETE USERCATALOG RECOVERY and doing a
       DEFINE of the new user catalog to the volume of your
       choice.  Many system programmers prefer to excercise a
       more tight control on where a user catalog resides for
       performance and tuning.  In an SMS managed environment,
       pre-defining an empty user catalog for an IMPORT will give
       you that control.
  ****************************************************************
  4). SHARED CATALOG CONSIDERATIONS:
  In a shared environment, you should always use the ALTER LOCK
  command to LOCK the catalog before using EXPORT and IMPORT.
  Use the UNLOCK parameter of IMPORT to unlock the catalog
  automatically when the IMPORT is complete.
     When you move a catalog to a different volume, you will need
  to update the UCAT connector information on each of the sharing
  systems.  The best way to do this is to use IMPORT CONNECT ALIAS
  with the OBJECTS and VOLUME keywords on each system.  This
  method will update the existing UCAT connect without disturbing
  the existing ALIAS entries.
  4a) The most common reason for Broken Catalogs, especially with
  duplicate keys, is improper catalog sharing.  Isuue a MODIFY
  CATALOG,ALLOCATED command from each system that is sharing the
  broken catalog and check that the 'R' flag is turned on.  Also
  be sure that the Share Options are set to 3,4 and that the
  volume where the catalog resides is genned as shared.
  ****************************************************************
  5). WHEN IMPORT FAILS...
  A failing IMPORT may leave a partial catalog structure, leading
  you to believe that the catalog is still present but damaged.
  The partial structure left is dependent on what parameters were
  specified, and is intended to preserve your ALIAS definitions,
  or prevent ENQUEUE lockouts arising from failing error recovery.
  Remember that you have an EXPORT copy, and things may look worse
  than they really are!  Don't panic, assess the damage -
    a.  Is the user catalog connector still present?  Use LISTCAT
        USERCATALOG to find out if the UCAT connector is present.
    b.  Are any of the catalog component (data, index) data sets
        present?  Use TSO OPTION 3.4, specify the volume.  If you
        were moving a catalog, check both the old and the new
        volumes.
  5a) IF EXPORT FAILS...
  Do a FULL VOLUME BACKUP and try to REPRO MERGECAT the catalog to
  a different catalog.  Then see what is left in the old catalog
  and REPRO that by level.  If you can get everything into the
  target catalog, you can then change your aliases to point to it
  or DELETE the old catalog for RECOVERY and reDEFINE and REPRO
  back into it.
  ****************************************************************
  6). COMMON Q/A PROBLEMS:
  Q:  My IMPORT failed, the catalog components are gone, the UCAT
      connector is still there, and my system is receiving
      messages that CATALOG ALLOCATE is failing.
  A:  Check your IMPORT statements and messages to see why IDCAMS
      failed.  Once you've corrected the problem, use EXPORT
      DISCONNECT to delete the connector, then rerun the IMPORT.
      ------------------------------------------------------------
  Q:  I ran EXPORT, and got an MSGICH408I that said I didn't have
      ALTER authority to the master catalog.  What happened?  The
      portable data set was created, it looked like it completed
      OK?   Is this a  security product (RACF) error?
  A:  The copy of the catalog only requires READ authority, but
      when we went to mark the catalog as "exported", you need
      ALTER.  Have your security administrator give you ALTER
      authority and rerun the EXPORT, otherwise your IMPORT may
      fail!
      ------------------------------------------------------------
  Q:  My EXPORT / IMPORT ran fine, CC=0, but all of my ALIAS
      entries are gone, what happened?
  A:  You didn't specify ALIAS on the IMPORT.  If you
      discovered it before anyone changed the catalog information,
      then add ALIAS to your IMPORT JCL and rerun the job.  If the
      catalog has changed, i.e.  entries added or deleted, then
      you must DEFINE each individual ALIAS.
      ------------------------------------------------------------
  Q:  My catalog IMPORT fails with MSGIEC614I RC192 (RSN192)
      DADSM CREATE failed (040343C9).  The EXPORT was clean and
      I know that there is enough physical space on the volume?
               (MSGIDC3009I RC68 IGG0CLEW RSN192)
  A:  Although SMS volumes were specified, the catalog had
      resided on NON-SMS managed volumes, thus, the EXPORTed
      datasets contained no SMS information.  Since no SMS
      STORAGECLASS or MANAGEMENTCLASS had been specified, DADSM
      failed the space allocation request because this was a
      NON-SMS request for space on an SMS managed volume.  This
      IEC614I message will appear in the failed jobs JESMSGLG
      (JOBLOG).  DADSM VTOC DATA SET SERVICES (VDSS1 VDSS2)
      ------------------------------------------------------------
  Q:  WHILE DOING B&R WORK ON MY UCAT,  I RAN DIAGNOSE, WITH
      INFILE POINTING TO MY UCAT, AND COMPAREDD POINTING TO
      THE VVDS.  ERRORS WHERE ISSUED BY DIAGNOSE NOTING :
        MSGIDC21364I RSN12 - CATLG and VVDS NAMES UNEQUAL
      THE BCS ERROR RECORD DISPLAY HAS AN OFFSET THAT POINTS
      TO A CATALOG VOLUME CELL RECORD (04).  IS THERE SOMETHING
      WRONG WITH THE VOLUME CONTAINING THE BCS or VVDS??
  A:  No.  The IDC21364I with RC12 diagnose record offset will
      always point to the BCS volume cell record.  But, the
      message is NOT saying that this particular record is at
      fault.  For RC12; there are four names in a VVDS record.
      The BCS entry and the VVDS entry do NOT have precisely the
      same names (length fields must also match) for one of the
      following four fields:
          . Record Name
          . Subrecord Name
          . Component Name (DATA or INDEX)
          . Catalog Name
       To recover from this error situation, if the Catalog names
       disagree,  remove the entries in the BCS by using the AMS
       DELETE with NOSCRATCH command option.
          At this point, if the VVDS record contains the desired
       catalog name, you can then catalog the dataset into the
       desired BCS by using the AMS DEFINE with RECATALOG command
       option;  otherwise, you can catalog the data set into the
       catalog indicated in the VVDS record.  (NOTE: it will be
       necessary to Redefine this catalog if it no longer exists.)
       Once this has been accomplished, all one need do is move
       the catalog record to the desired catalog by use of the AMS
       REPRO MERGECAT command.
          (NOTE: If you use straight REPRO (NOMERGECAT is default)
       to copy one catalog to another,  the VVDS VVR records are
       changed to point to the TARGET (output) catalog,  and all
       subsequent processing related to this cataloged information
       MUST be done under the TARGET catalog).
          If the names that disagree are not catalog names, and
       if the VVDS record is correct, then remove the entries
       from the BCS by using the AMS DELETE with NOSCRATCH option.
       Followed by the DEFINE with RECATALOG option.
          If the VVDS VVR record is incorrect, remove the dataset
       by using the AMS EXPORT command.  Now, you can import the
       data set using the AMS IMPORT command with the desired
       NEWNAMES parameter.
          See your  Managing Catalogs  manual for more information
       related to the IDCAMS DIAGNOSE operation.
       -----------------------------------------------------------
  Q:  WHILE DOING CATALOG RECOVERY,  I ISSUE AN  IDCAMS
      DEFINE USERCATALOG COMMAND.  THE DEFINE FAILS WITH CC12.
      ASSOCIATED ERROR MESSAGES IN THE SYSLOG AND JESMSGLG ARE:
         MSGIEC161I  020-54 (RC20 RSN54 OPEN ERROR)
         MSGIDC3016I CATALOG IS NOT AVAILABLE
         MSGIDC3009I RC04 RSN2 (IGG0CLES -2)
      THE ERRORS IMPLIES THAT THERE IS A STORAGE SHORTAGE, EITHER
      REGION OR SQA.  I HAVE NO SUCH SHORTAGES.
  A:  Previous errors may have caused the Catalog Address Space
      to get out of sync.  First issue CAS / MVS command :
         MODIFY CATALOG,RESTART
      then retry the AMS DEFINE UCAT operation.
  CATBREAKER  VSAMINFO  DB2INFO  disaster backup recovery testing
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• INFO APAR CAN FOR RETENTION / PIN
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels