Hi,

You can try this, create a library called syscat, the command is as follows:

CRTLIB LIB(SYSCAT)

This will automatically create it in the QSYS library. Then copy the SYSIBM
objects to this library. If you have an existing SYSCAT library, it should
complain that you have it or the SYSCAT you are creating will not go to the
QSYS library. (You can do a WRKLIB SYSCAT command before creating it to
verify if it is existing. Be careful overwriting any existing objects that
are already existing. I suggest if something is existing, consult your
aS/400 admin.

This may just answer the question on SYSCAT being hard coded in ER Win. You
may encounter other errors.

Thanks,

RdR

"Sulu's Beard" <wilbolite@nospam.yahoo.com> wrote in message
news:8ssv51tj60q9of77l8sij5dp45b3ateu14@4ax.com...
> Hey gang,
>
> I'm evaluating the CA ERWin product for an upcoming data warehousing
> project. I'm most excited about the reverse engineering aspect of
> this system.
>
> I've sucessfully tested it on a SQL Server 2000 system, however, when
> I run it against our iSeries DB2 system (on which our ERP exists), I
> encounter errors that essentially say that files are missing from our
> SYSCAT library. I'm not an iSeries expert, but I can say that the
> SYSCAT library does not exist on our box, and that the tables ERwin is
> looking for is actually stored in a SYSIBM library.
>
> I've checked all sorts of help files & on-line searches, but I've
> found no way to tell ERwin to look in SYSIBM instead of SYSCAT. It
> seems almost as if SYSCAT is hard-coded into this application.
>
> Any ideas?
>
> - Bill