Migration << >>

Troubleshooting the MEMO Source Extractor

This section explains how to respond to error messages produced by the UserList function, the Migrate Users function, or both functions.

Error message identifications that end with E indicate serious errors for which the MEMO Source Extractor will issue forced abends (S0CB).

Invoking MEMO and MEMO/API programs may also generate error messages. These error messages are documented in the MEMO Reference Manual and the MEMO/API manuals.

UserList Error Messages

This section lists all of the UserList error messages and explains how to resolve them.

MIGGENU0100E Invalid mode type

MIGGENU0103E Mode field missing from MIGPARM1

MIGGENU0104E Mode field blank in MIGPARM1

These error messages indicate invalid or missing entries in the mode field of the MIGPARM1 instream data. In the mode field, you must enter either R for Remote or M for Mailbox.

   To correct the mode field entry

  1. Edit MIGGENU in the MEMO Source Extractor JCL library.
  2. In the MODE field of the MIGPARM1 instream data, specify R or M.
  3. Submit job MIGGENU.

MIGGENU0105E Primary field missing from MIGPARM1

MIGGENU0106E Primary field blank from MIGPARM1

MIGGENU0107E GCID field missing from MIGPARM1

MIGGENU0108E GCID field blank from MIGPARM1

MIGGENU0109E No records on MIGPARM1

These error messages indicate one or more fields in the MIGPARM1 instream data with blank or missing profile information.

   To add blank or missing profile information

  1. Edit MIGGENU in the MEMO Source Extractor JCL library.
  2. Add the missing MIGPARM1 profile information in the mode, primary, or GCID fields, as follows:

    3. MODE
    Specify M (mailbox) or R (remote user).

    PRIMARY
    Specify the name of the PC file used for the extracted information file MIGPRIM1 produced by the MEMO Source Extractor. This name must correspond to the name to be used during the PC-TSO file transfer. For example: primary.pri.

    GCID
    Specify the Graphic Character Identification (GCID) code-page that will hold the extracted information on the PC. Its standard value will be 850, the multilingual code-page. For example: gcidcodepage.

  3. Submit job MIGGENU.

MIGGENU0101E No records on MIGACCT

MIGGENU0102E Not all required fields specified in MIGACCT

MIGGENU0110E No users found to migrate

These error messages indicate a missing or inadequate list of users to be migrated to Microsoft Exchange Server.

   To add or change a list of users

  1. Edit MIGACCT in the MEMO Source Extractor library.
  2. Specify the users to be extracted. (Refer to the "Performing the Migration" section earlier in this chapter.)
  3. Submit job MIGGENU.

Migrate Users Error Messages

This section lists all of the Migrate Users error messages and explains how to resolve them.

MIGMIGU0200E No records on MIGPARM2

MIGMIGU0201E Primary field missing from MIGPARM2

MIGGENU0202E Primary field blank from MIGPARM2

MIGMIGU0203E Secondary field missing from MIGPARM2

MIGGENU0204E Secondary field blank from MIGPARM2

MIGGENU0205E GCID field missing from MIGPARM2

MIGGENU0206E GCID field blank from MIGPARM2

These error messages indicate that one or more fields in the MIGPARM2 instream data have missing profile information.

   To add missing or blank information to fields

  1. Edit MIGMIGU in the MEMO Source Extractor JCL library.
  2. In MIGPARM2, add the missing information in the primary, secondary, or GCID fields, as follows:

    3. PRIMARY
    Specify the name of the PC file used for the extracted information file MIGPRIM2 produced by the MEMO Source Extractor. This name must correspond to the name used during the PC-TSO file transfer. For example, primary.pri.

    SECONDARY
    Specify the name of the PC file used for the extracted memo text file MIGSEC. This name must correspond to the name used during the PC-TSO file transfer. For example: secondary.sec.

    GCID
    Specify the Graphic Character Identification (GCID) code-page that will hold the extracted information on the PC. Its standard value will be 850, which is the multilingual code-page. For example: gcidcodepage.

  3. Submit job MIGMIGU.

MIGMIGU0207E No users on MIGUSER

You have not specified which users to migrate to Microsoft Exchange Server.

   To specify which users to migrate

  1. Edit MIGMIGU in the MEMO Source Extractor JCL library.
  2. Specify the users to be migrated. (Refer to the "Performing the Migration" section earlier in this chapter.)
  3. Submit job MIGMIGU.

MIGMIGU0208E Error calling MEMO/API

An error occurred in MEMO/API. Refer to your MEMO/API manual and look up the return code displayed with this error message.

MIGMIGU0209E Error signing user onto MEMO--processing continues onto next user

This error message indicates that the MEMO Source Extractor cannot log a MEMO user on to MEMO/API. This can occur for either of these two reasons:

You avoid these problems if, before migration, you perform all the tasks discussed in the "Installing the MEMO Source Extractor" section, earlier in this chapter. Before migration, you specify users as MEMO/API users and reset user passwords to match MIGUSER passwords (so that users cannot log on during migration).

MIGMIGU0210W User has more than 10,000 mail items in maillog

A user has more than 10,000 items in their maillog. The MEMO Source Extractor processes only the first 10,000 items. If you need to migrate more than 10,000 items for a particular user, follow these steps:

   To migrate more than 10,000 mail items

  1. Delete the 10,000 mail items already migrated to Microsoft Exchange Server.
  2. To migrate an additional 10,000 mail items, re-run the migration process for the user.

MIGMIGU0211W Mail item has more than 70 recipients

This is a warning message only. The mail item will migrate to Microsoft Exchange Server with only the first 70 recipients.

MIGMIGU0212W Mail item is too large

This is a warning message only. The mail item is too large to process, so processing will continue with the next mail item. The MEMO Source Extractor supports the maximum text size currently supported by MEMO (500K).

UserList and Migrate Users Error Messages

These error messages are produced by both the UserList and Migrate Users functions.

MIG 9000E Error on open/close file

MIG 9001E Error on reading file

MIG 9002E Error on writing file

Each of these error messages specifies the file with the error and the return code from the I/O call. For example, if an open error occurred on MIGACCT (return code 39) while running the UserList function MIGGENU, the following data would be output to the job log. (Refer to your COBOL II manuals for information about file return codes.)

PROG-ID: MIGGENU COMPILED: 06/08/9411.10.05

PROG-ID: MIGERR COMPILED: 05/26/9415.41.48

========MIGGENU ========

MIG 9000E Error On Open/Close File

-----------------------------------------------------------------

MIGACCT 39

DCCCDDE44FF444444444444444444444444444444444444444444444444444444

49736530039000000000000000000000000000000000000000000000000000000000

--- VS COBOL II ABEND Information ---

MIG 9999E Message not found on file. See below.

This error message indicates that the error message to be displayed cannot be found in the error message file MIGCUST. This happens if the MEMO Source Extractor error messages were customized incorrectly. You can only customize the text of an error message, not the error message number.

The error message specifies the error message key, which could not be found. For example:

PROG-ID: MIGGENU COMPILED: 06/08/9411.10.05

PROG-ID: MIGERR COMPILED: 05/26/9415.41.48

MIG 9999E Message not found on file. See below.

FILE : CUSTMFIL KEY : M01000 RC : 23

========MIGGENU ========

--- VS COBOL II ABEND Information ---

   To correct error messages

  1. Edit MIGDCUS2 and check that all error messages have correct error message numbers as listed in Figure 2.6 in the "Installing the MEMO Source Extractor" section, earlier in this chapter. Change any incorrect error message numbers.
  2. Save MIGDCUS2.
  3. Run JCL job MIGCUST.