>In moving data from one z/OS system to another, I have somehow hosed up a
>catalog. The orignal system was at z/Os 1.10, the new system is at 1.12. I
>moved 8 3390 volumes using ADRDSSU dump and restore, and this looked like it
>worked well. One of the 3390's I moved had a user catalog on it that
>contained the catalog entries for the datasets on the moved volumes. I
>executed an IMPORT CONNECT to connect the ADCD system's master to the user,
>then did DEFINE ALIAS for the alias entries. Everything looked good at this
>point. I could find my existing datasets on the volumes using the catalog.
>Up until then I was working as IBMUSER.
>
>I logged off and logged back on with one of the new TSO userid's defined on
>the 1.12 system. The logon id was the same as one defined on the 1.10 system.
> Almost immediately started getting various errors when trying to allocate new
>datasets using ISPF 3.2 with a hlq that would match one of the alias entries
>in the user catalog. The errors would occur if I did not specify a volser on
>the allocate. If I directed it towards a volume, as long as space was on the
>volume, everything was ok. The goofy part about this is that I would get
>error messages on my TSO terminal indicating an error while trying to
>allocate, but after hitting the enter key, the dataset would get allocated.
>
>My thought was that a 1.10 catalog was not compatible with 1.12, and that I
>had screwed up by just doing the IMPORT CONNECT on the existing catalog that
>came with the volume restore. But I can't get rid of it. Everything I try
>fails. Early on I did an EXPORT of the catalog, and that worked fine. I then
>tried an IMPORT, since the manual states the catalog is deleted and re-defined
>in this operation, but the IMPORT
>fails. Error says it cannot open the catalog.
>
>I then deleted the alias entries for the user cat, and did an EXPORT
>DISCONNECT of the user cat from the master cat. Return code 0 from both. I
>then defined another user cat on a different volume, and tried an IMPORT of
>the exported copy. Job got errors. The original user cat was named
>UCAT.CATALOG1 on volume VPWRKF. The new user cat is UCAT.CATALOG on volume
>SCSYS1. Am getting these errors from the job:
>
I would look at the esoterics, acs routines.
Does the Ucat on 1.10 have the same esoteric name in the 1.12 system? Does it
define the same volume type that it was backed up from?
Does the ACS code on 1.10 provide the same elements under 1.12?
Did you indicate NOSMS in the DFDSS restore? NULLMGMTCLAS or NULLSTORCLAS or
BYPASSACS(dsn{,dsn...})}
Lizette
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
