XFOR: AS/400 DXA on RISC Computer

Last reviewed: January 30, 1998
Article ID: Q166847
The information in this article applies to:
  • Microsoft Exchange Server versions 4.0, 5.0, and 5.5

SYMPTOMS

The AS/400 directory synchronization agent that ships with Microsoft Exchange Server5.0 can only run on a CISC AS/400 because four of the objects do not convert automatically from 48-bit to 64-bit.

RESOLUTION

To resolve this problem and run the AS/400 DXA on a RISC computer:

  1. The tape provided contains four objects to replace the four objects currently located in the DXA400 library.

    These objects are:

          ADDDAT, ADDTIM, TAADATAC, TAATIMAC
    

    Use the command DLTOBJ to delete the four objects mentioned above from the DXA400 library, and use the command RSTOBJ to retrieve the four objects from the tape to the DXA400 library.

  2. The AS/400 DXA uses the command DSPDIR, which has been replaced by DSPDIRE. In order for the AS/400 DXA to access the AS/400 directory, copy the DSPDIR object from QSYS/DSPDIRE to DXA400/DSPDIR.

  3. The physical file QRYDST with member QRYDST has maximum record length of 246 when it should be 251. The following command re-creates the file with the proper record length:

          CRTPF FILE(DXA400/QRYDST) RCDLEN(251)
    

MORE INFORMATION

This behavior is by product design. \

Keywords          : XFOR kbsetup kbusage
Version           : WinNT:4.0,5.0,5.5
Platform          : winnt
Issue type        : kbprb
Solution Type     : kbworkaround


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 30, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.