Migration | << | >> |
---|
This section explains how to migrate users, whether at one time or in multiple steps, and how to run the two primary MEMO Source Extractor functions, UserList and Migrate Users.
UserList allows you to add groups of MEMO users as either Microsoft Exchange Server mailboxes or remote users. The Migrate Users function allows you to migrate MEMO users to Microsoft Exchange Server.
Important After migration but before the MEMO maillogs are deleted, you should have the users migrate any important information that was not migrated. The MEMO Source Extractor does not migrate the following information: binary files, personal address information, calendar information, bulletin boards, and distribution lists.
You must first decide whether to migrate all MEMO users at one time or in multiple steps. Depending on which type of migration you choose, you would use the following procedures, which are explained in more detail in later sections.
To perform single-phase migration
JH | PASSWORDMEMOIMI |
DLB | PASSWORDMEMOIMI |
To perform multi-phase migration
JH | PASSWORDMEMOIMI |
DLB | PASSWORDMEMOIMI |
You run the UserList function by submitting an MVS batch job MIGGENU, from the MEMO Source Extractor JCL library. This creates output files with the memo-IDs of the users to be migrated.
Input files | ||
---|---|---|
MIGPARM1 | Parameter information | Sequential (fixed length) |
MIGUSRL | List of MEMO users | Sequential (variable length) |
MIGACCT | List of users to be generated | Sequential (variable length) |
MIGCUST | Control file | VSAM | Output files |   |   |
MIGPRIM1 | Migration data to be sent to Microsoft Exchange Server | Sequential (fixed length) |
MIGPACK | Configuration information used by Microsoft Exchange Server | Sequential (fixed length) |
You run UserLists for both mailboxes and remote addresses:
You assign mailboxes to MEMO users to be migrated to Microsoft Exchange Server. Each user will have a Microsoft Exchange Server account, created by the Microsoft Exchange Server Migration Assistant.
You assign remote addresses to MEMO users who will remain on MEMO but want to communicate with Microsoft Exchange Server. These remote addresses are registered on Microsoft Exchange Server by the Microsoft Exchange Server Migration Assistant.
To run the UserList function, you must specify profile information in MIGPARM1, and users in MIGACCT.
To run the UserList function, you specify profile information in MIGPARM1. MIGPARM1 is specified as instream data in the JCL job MIGGENU.
You type 10 characters in the fields. The data for the fields can be up to 70 characters. The order of the records does not matter. MIGPARM1 has the following fields:
MODE
Specify M to create mailboxes, or specify R to create remote addresses.
PRIMARY
Specify the PC file name for MIGPRIM1, the extracted information file 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, which holds the extracted information on the PC. Its standard value will be 850, which is the multilingual code-page. This value should correspond to the code-page to which your PC-TSO file transfer program will convert when converting from EBCDIC to ASCII. For example: gcidcodepage.
When using the UserList program in either mode, you specify the group of users to be extracted from MEMO in the sequential dataset MIGACCT. The fields on the records are separated by a comma, followed by a space. MIGACCT has the following fields:
DGN
Specify the distribution group name (1 to 8 characters), or * for all MEMO users. (Mandatory)
MEMOID
Specify the name of a user's mailbox (1 to 8 characters), or * for all memo-IDs within a particular DGN. (Mandatory)
The user control file MIGACCT allows you to extract specific users, specific distribution groups, or all MEMO users.
Specific Users To extract specific users, add a MIGACCT record for each user to be extracted. Each record specifies one MEMO user. For example, if you specify MEMOIMI, KD, MEMOIMI, SJS, and MEMOIMI, SJG, only users KD, SJS, and SJG will be extracted.
Distribution Groups To extract distribution groups, add a MIGACCT record for each distribution group to be extracted. The MEMOID for each record must be *. For example, if you specify MEMOIMI, * and MEMMICRO, * all users for distribution groups MEMOIMI and MEMMICRO will be extracted.
All Users To extract all MEMO users, add only one MIGACCT record with DGN set to *. As all users are to be extracted, the value of MEMOID will be ignored by the MEMO Source Extractor. For clarity, you should also set MEMOID to *.
The MIGACCT dataset will be created as part of the installation process. MIGACCT will contain a sample record that shows how to extract all users. The sample MIGACCT created can be edited by using the TSO editor.
To run the UserList Function MIGGENU
MODE
Specify M for mailbox, or specify R for remote.
PRIMARY
Specify the name of the PC file used for the extracted information file MIGPRIM1.
GCID
Specify the GCID code-page that will hold the extracted information on the PC.
This process will migrate the lists of MEMO users to Microsoft Exchange Server. The mail messages are processed one at a time. The Migrate Users function examines the MEMO maillog for each user specified. (Only memos are migrated; binary files are ignored.)
You start by submitting the MVS batch job MIGMIGU, from the MEMO Source Extractor JCL library.
Input files | ||
---|---|---|
MIGUSER | List of users to be migrated | Sequential (fixed length) |
MIGPARM2 | Profile information | Sequential (fixed length) |
MIGUSRV | List of MEMO users | VSAM |
MIGCUST | Control file | VSAM |
Output files |   |   |
MIGPRIM2 | Profile information of migrated memos | Sequential (fixed length) |
MIGSEC | Text of migrated memos on Microsoft Exchange Server | Sequential (fixed length) |
MIGPACK2 | Configuration information used by Microsoft Exchange Server | Sequential (fixed length) |
To run the Migrate Users function, you must specify the profile information in MIGPARM2, and the users in MIGUSER.
MIGPARM2 is specified as instream data in the JCL job MIGMIGU. You type 10 characters in the fields. The data for the fields can be up to 70 characters. MIGPARM2 has the following fields:
PRIMARY
Specify the PC file name that will be given to MIGPRIM2, which contains the extracted memo header information 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.
SECONDARY
Specify the PC file name that will be given to MIGSEC, which contains the extracted memo text produced by the MEMO Source Extractor. This name must correspond to the name to be 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. This value should correspond to the code-page to which your PC-TSO file transfer software will convert when converting from EBCDIC to ASCII. For example: gcidcodepage.
MIGUSER specifies the list of users to be migrated. MIGUSER is specified as instream data in the JCL job MIGMIGU. You cannot migrate mail for all users by using wildcard values for MEMOID and DGN. MIGUSER has the following fields:
MEMOID
Specify the name of the user's mailbox (8 characters, fixed length). (Mandatory)
PASSWORD
Specify the user's password (8 characters, fixed length). (Mandatory)
DGN
Specify the distribution group name (8 characters, fixed length). (Mandatory)
SAF-ID
Specify the security ID (8 characters, fixed length). (Optional) If external security is used to validate MEMO users, the SAF-ID field can specify the external security ID.