Chapter 2: Prepare the Mainframe
The following tasks should be completed by the systems programmer.
The GroupWise* Gateway for OfficeVision/VM** is defined to VTAM** as a physical unit Type 2 with a Type 0 single logical unit (LU) gateway definition. The VTAM definition can be created using a token ring or an SDLC physical connection.
The VTAM and RSCS definitions used in this chapter are examples only. Your site or network standards may require alterations in certain labels or parameters. Underlined sample parameters affect gateway configuration and should be recorded on the worksheet for the GroupWise administrator. VTAM and RSCS definitions should only be modified by a systems programmer.
Define
a Logon Mode Table Entry (MODEENT)
Define a Logon Mode Table Entry (MODEENT) before you activate the
VTAM definition required by your physical connection type. Add a complete
Logon Mode Table or add the MODEENT statement to an existing table.
Assemble and link-edit the table into the appropriate VTAM LOADLIB (for
example VTAMUSER LOADLIB). The MODETAB and MODEENT statement labels must
match the labels in the PU MODETAB and DLOGMOD parameters defining your
gateway connection.
Enter the MODEENT parameters exactly as shown below. The worksheet value is underlined.
| WORKSHEET
Under Item 1: Logon Mode Entry, enter the entry from the MODEENT statement label. |
Connect
via Token Ring NCP
Create a VTAM Switched Major Node Definition for the gateway. Make
sure it is recognized by VTAM using the NCP token ring Interconnect (NTRI)
feature of your 37xx.
The worksheet values are underlined.
| WORKSHEET
Record the following values on the worksheet: Item 4: Physical Unit (IDBLK) Item 5: Physical Unit (IDNUM) Item 6: Logical Unit Name (LU name) Item 7: Logical Unit Address (LOCADDR) |
Connect
via SDLC
Specify LINE, PU, and LU definitions to the NCPGEN file (see the
following example) to identify the gateway using an NCP-attached SDLC
line. The LINE ADDRESS you specify depends on the 37xx physical line you
selected for your connection.
The worksheet values are underlined.
| WORKSHEET
Record the following values on the worksheet: Item 2: SDLC Line Encoding Item 3: Physical Unit Address Item 6: Logical Unit Name (LU name) Item 7: Logical Unit Address (LOCADDR) |
To define the gateway to RSCS, adjust the LINK statement for each gateway and a ROUTE statement for each GroupWise post office in the RSCS CONFIG file. You can use wildcard characters.
Adjust
the LINK Statement
The LINK statement links the RSCS service machine and the VTAM
resource. The following example shows a link for the sample used
throughout this guide.
Adjust
the ROUTE Statement
The ROUTE statement creates a path between RSCS and the GroupWise
post offices. Include the name of each post office or its alias, and the
link ID from the gateway LINK statement. The following example
establishes the route to the post offices used throughout this guide.
Conform
to Naming Conventions
RSCS only recognizes GroupWise post offices that follow the RSCS
eight-character naming convention. In the example used in this guide, the
GroupWise post office ADVERTISING exceeds the eight-character limitation.
Such names must be assigned an eight-character alias by the GroupWise
administrator. ADVERT is a valid alias for the Advertising post office in
this example. For more information, see Create
a Post Office Alias in Chapter 6: Send a Message from the
Mainframe to GroupWise Users.
Define the GroupWise Post Offices to OfficeVision/VM (Optional)
To use the .REF command in OfficeVision/VM, add entries for each post office to the REMLOC file. To use cross-calendar checking, add entries for each post office to the REMCAL file. For more information, see Chapter 8: Set Up Busy Search.
Adjust
the REMLOC File
To use the .REF command, adjust the REMLOC file. The following
example shows the modified REMLOC file for the examples in this guide.
| ADVERT | ADVMAIL | ADVT |
| VM1 | VM1MAIL | VM1T |
GroupWise post offices with names exceeding eight characters must be assigned an eight-character alias by the GroupWise administrator.
Adjust
the REMCAL File
To perform cross-calendar checking, adjust the REMCAL file. The last
character in for each REMCAL entry must be an R; it tells the calendar
machine to use RSCS for cross-calendaring to GroupWise. The following
example shows the modified REMCAL file used in examples in this guide.
| ADVERT | ADVCAL | ADVTR |
| VM1 | VM1CAL | VM1TR |
GroupWise post offices with names exceeding eight characters must be assigned an eight-character alias by the GroupWise administrator.
Adjust
the Timeout Option
Set the OfficeVision/VM Timeout option to a minimum of five minutes
to allow adequate time for busy checks. For more information, see Performance
Aids: Changing Communication Timer in the OfficeVision/VM manual.
Verify
VM Compatibility
Because the gateway uses RSCS to communicate between GroupWise and
OfficeVision/VM, you must have an XA-compatible system to cross-calendar
check.
* Novell trademark. ** Third-party trademark. See Trademarks for more information.