Chapter 6: Send a Message from the Mainframe to GroupWise Users

• Conform GroupWise to VM Restrictions
  
  
• Send a Message from OfficeVision/VM to GroupWise
  
  
• Send a Message from CMS to GroupWise

Conform GroupWise to VM Restrictions

GroupWise* facilities, such as domains, post offices, and user IDs, can have names that are longer than eight characters. For example, the post office name used in this guide is Advertising, which is eleven characters long. The VM operating system requires that no name exceed eight characters in length. This means OfficeVision/VM** users cannot address GroupWise users whose post office names or user IDs exceed eight characters.

You can avoid this problem by assigning an alias to a post office or an alias to a user who does not conform to the VM restrictions. The following instructions explain how to create a post office and user alias.

Create a Post Office Alias
A post office alias is required for any GroupWise post office name that exceeds eight characters. To create a post office alias,

1. From NetWare Administrator, click Tools  GroupWise View  right-click the object you want to assign an alias to  click Details.
   
   
2. Click the Aliases page  Add
   
   
   
   
3. Fill in the fields:
   
   Gateway Alias Type: Use the browse button to select the correct alias type. For this gateway choose OVVM.
   
   Gateway Alias: Enter an eight-character alias name for this object.
   
   
4. Click OK.
   
   
5. Have the mainframe system programmer add the alias name to the RSCS CONFIG file. No messages can be exchanged using this post office until the RSCS CONFIG file has been updated.

Create a User Alias
A user alias is required for each user whose user ID exceeds eight characters. To create a user alias,

1. From NetWare Administrator, click Tools  GroupWise View  right-click the user object you want to assign an alias to  click Details.
   
   
2. Click the GroupWise Aliases page  Add
   
   
   
   
3. Fill in the fields:
   
   Gateway Alias Type: Use the browse button to select the correct alias type. For this gateway, choose OVVM.
   
   Gateway Alias: Enter an eight-character alias name for this object.
   
   
4. Click OK.
   
   

Send a Message from OfficeVision/VM to GroupWise

Use the following options to send a message form OfficeVision/VM to GroupWise.

Addressing Without a Nickname File
If OfficeVision/VM users send messages to GroupWise users who are not part of the OfficeVision/VM nickname file, the syntax is:

post office(user ID)

If Maria, an OfficeVision/VM user, sends a message to Christopher, a GroupWise user in the Advertising post office, the syntax is:

advert(chris)

In this example, the GroupWise post office name and user ID exceed eight characters, so the GroupWise administrator would have to assign an alias, ADVERT, and a user alias, CHRIS, before OfficeVision/VM users could send messages.

Addressing with a Nickname File
OfficeVision/VM users frequently use a nickname file to shorten addressing syntax. The GroupWise address book can be sent to the mainframe in the nickname format if GroupWise Directory Synchronization is enabled. See Define Optional Gateway Settings in Chapter 10: Enhance Gateway Functionality for more information. This file could either be merged into the existing nickname file or kept separate. See Define OV/VM Parameters in Chapter 10: Enhance Gateway Functionality for more information.

If a nickname file is used, the syntax for an OfficeVision/VM user to send a message to a GroupWise user is:

user

If Maria, an OfficeVision/VM user, wanted to send a message to Christopher, a GroupWise user in the Advertising post office, the syntax is:

chris

In this example, the GroupWise post office name and the user ID exceed eight characters. The GroupWise administrator would have to assign an alias, ADVERT, and a user alias, CHRIS, before OfficeVision/VM users could send messages. These aliases must then be added to the nickname file. See your OfficeVision/VM documentation for more information on nickname files.

Understanding OfficeVision/VM Dot Commands
OfficeVision/VM uses dot commands to enhance message functionality. The gateway supports the dot commands shown in the following table.

* Consult with the OfficeVision/VM administrator.

The new dot commands, shown in the following table, apply only when OfficeVision/VM users send messages to GroupWise users.

In the case of .SE and .PR, when the default values are not selected, a banner appears at the top of the message body explaining which argument was used. The message body can display as many dot command argument banners as you request.

The following dot commands for the WP PROFS** 1.0 Gateway are no longer supported:

• .EC
• .LA
• .LABC
• .LACC
• .ATT

Send a Message from CMS to GroupWise

The following CMS functions can be used to communicate with GroupWise users through the gateway:

• Note
  
  
• Tell
  
  
• SendFile (sf)
  
  
• List Processing
  
  

Using the CMS Names File
The mainframe system programmer maintains the CMS System Names file.

The GroupWise users you address using CMS do not need to be part of this file. You can also use the CMS group option to include groups of users. For information about adding users and groups to the System Names file, refer to the VM reference manual that covers CMS operations.

The CMS System Names file is different from the OfficeVision/VM nickname file.

CMS Note
A user can use the CMS Note feature to send messages created through the CMS Note Power Input.

The Note program starts when you type a valid CMS Note command and address string at the ready prompt. For detailed information about how to use the Note program, consult the CMS Online Help by typing help note at the CMS ready prompt or at the Note prompt, or consult your mainframe programmer. The following table lists some CMS Note addressing options.

The gateway supports CMS Note command line parameters such as ACK, NOACK, SHORT, and LONG.

CMS Tell
A user can use CMS Tell to send brief messages without using a text editor.

The following table lists the addressing options.

CMS Sendfile
A user can use the CMS Sendfile to send objects, such as files, to GroupWise. The files arrive as attachments to GroupWise messages. The gateway converts EBCDIC files to ASCII text; other file types arrive unchanged.

The following table lists possible addressing options. The commands enclosed in square brackets ([ ]) are required; those in French braces ({}) are optional.

Using NJE List Processing
OfficeVision/VM users can send files to GroupWise users using NJE list processing. To enable NJE list processing, the mainframe system programmer must first define a listproc link type to the RSCS service machine. For more information about how to define this link type, consult your VM manual.

Using NJE List Processing, users can send files from the ready prompt or with a REXX EXEC. The list processing feature is more efficient than the CMS Sendfile when you send a file to multiple users. List processing sends one copy of the file; CMS Sendfile sends one copy to each recipient. List processing distributes messages using an NJE distribution list file. The following section explains how to create a distribution list file. For detailed information, refer to the RSCS reference manual.

The NJE list file, created using xedit, contains the user IDs or CMS nicknames of every member of the group.

2 Advert Bob
This is the message you requested
Hope it will help
Advert Chris

The 2 that precedes Bob’s name represents the number of lines of text that follow the user’s name. These lines appear as a GroupWise message; the files arrive as a separate GroupWise message.

Every list file must end with a blank line. There is no limit to the number of distribution list files you can create or to how many users can be in each file. You can also combine VM and GroupWise users and their nicknames or group nicknames in the list.

* Novell trademark. ** Third-party trademark. See Trademarks for more information.