LAN-based clients are installed and configured using the PC setup application. This application is distributed on CD ROM. The self extracting file solstice.exe is the SMCS front end installation file for PROFS channels. It contains the SMCS client setup.exe program. This file needs to be executed on a PC. The location of this file on the CD is:/products/sims/win16/solstice.exe
The CD has a Windows 95/NT readable partition which will allow you to copy this file into a DOS/Windows based system.
There are lists of files which need to be installed on the IBM mainframe. The location of these files on the CD is:
Note - The Windows-based setup.exe application is used to set up the PROFS/NJE client on an OS/2 server. Setup.exe appears in the Program Manager window of the OS/2 system.
After client setup is complete, the setup application is installed in a Windows program group so that you can revise your PC clients setup as needed.To install the client setup program, do the following:
1. |
2. | Choose Continue. |
Indicate that you want to install the PROFS channel. Choose the PROFS channel only if you are on an OS/2 machine (see FIGURE 2-2). |
Note - You can install both Microsoft Mail and cc:Mail on the same PC.
3. |
Configuring PROFS/OfficeVision |
1. | Create the DirSync Service Machine userid. |
The name of the DirSync/VM userid is assumed to be DIRSYNC, but can be any valid VM userid. Define a VM userid like the one below, inserting any site specific directory statements, and changing the lower-case options with your own values. |
USER DISRYNC pw 8M 8M G | ||
ACCOUNT SUNSOFT SUNSOFT | ||
MACHINE XA | ||
IPL CMS PARM AUTOCR | ||
CONSOLE 009 3215 | ||
SPOOL 00C 2540 READER * | ||
SPOOL 00D 2540 PUNCH A | ||
SPOOL 00E 1403 A | ||
LINK MAINT 190 190 RR | ||
LINK MAINT 19E 19E RR | ||
LINK ov_admin vad 399 RR | ||
MDISK 191 3390 2944 10 RAM119 MR |
Note - ov_admin is the OfficeVision/VM system administrator userid, usually SYSADMIN. vad is the virtual address of the common OV/VM minidisk, usually the 399 disk.
2. | Log in to the DirSync/VM userid via the terminal emulator running on OS/2. |
The product you have received is in PC/DOS file format. |
3. | Transfer the following files to this userid in binary mode using the OS/2 terminal emulator. |
CONFIG EXE | ||
DIRSYNC EXE | ||
GETVAFM$ EXE | ||
PROFILE EXE | ||
UAD2DIRS EXE | ||
VMUSER$ EXE | ||
DIRSYNC TXT | ||
EAGALUME TXT | ||
DIRSYNC DAT | ||
DIRSYNC HEL | ||
EAGALPRC MOD | ||
EAGRTALT MOD | ||
CONFIG XED | ||
DIRSYNC XED | ||
WAKEUP TIM | ||
EAGALUME REP | ||
README TXT |
Dirsync.txt and readme.txt can be transferred in text mode. You need to remap the extension name of the files to the file type in the CMS environment. The name remapping is as following (see TABLE 2-1):
|
4. | Ensure that the WAKEUP module is available. |
5. | Type CONFIG and press Enter. |
6. | Enter the appropriate information in the fields and press Enter to save the configuration data. |
For a detailed explanation of each configuration option press the Help key (F1). |
7. | Add the statement 'AUTOLOG DIRSYNC pw' to AUTOLOG1's PROFILE EXEC so the DirSync userid will get logged on when the system is IPL'd. |
If your site has a facility which automatically forces off idle users, exclude the DirSync userid. |
8. | Add the DirSync/VM Service Virtual Machine to the OfficeVision/VM UAD file. |
For information on adding users to the OV/VM UAD file see information on the UAD INPUT command in the OV/VM Managing manual. |
If the REXX/370 runtime libraries release 3 or above are not available you will need to do the following.
a. | Rename EAGALPRC MODULE A to EAGRTPRC MODULE A |
b. | Rename EAGALUME TXTAMENG A to EAGUME TXTAMENG A |
c. | Add the following statement to the DirSync/VM SVM's PROFILE EXEC. 'PIPE CMS NUCXDROP EAGRTPRC' |
The initial DirSync/VM directory can be created from an existing OfficeVision/VM UAD file via the UAD2DIRS utility. UAD2DIRS will prompt for the userid and virtual address where the OFSUAD FILE file can be found. It links/accesses the disk and extracts the userid, node, user's full name, department, appropriately formats it, and writes it to the telephone directory specified on the CONFIG screen. To run the UAD2DIRS utility, type UAD2DIRS at the CMS Ready prompt on the Dirsync service machine. The DIRECTRY file will be written to the SUNSOFT A disk. Move it to the appropriate phone directory disk, usually SYSADMIN 397.
If the DirSync machine needs to be started manually it can either be autologged or you can log on to it. If you log on to it, three options are presented.
Configure | ||
Start DirSync | ||
Exit |
Enter the following directory sync parameters:
Export Schedule time: Enter the scheduled time for exporting directory information to the central directory. | ||
Import Schedule time: Enter the scheduled time for importing directory information from the central directory to the local telephone directory. | ||
OV/VM Telephone directory location: Enter the userid and virtual address which contains the OV/VM telephone directory. It usually is the SYSADMIN's 397 disk. | ||
OV/VM Telephone directory password: Enter the read/write password of the telephone directory. | ||
OV/VM Telephone directory name: Enter the name of the telephone directory which is just created and moved in the last step. |
Note - Either fill out the table in Appendix A or create a table first before the following field.
Dirsync mail address: Enter the PROFS address of the SMCS PROFS channel dirsync manager (for example, DPROFSJ). This field must match the channel_name on the server and the node_name on the client setup. | ||
Administrators: Enter the userid(s) of local users with the administrative authority. The first administrator listed is the primary administrator, the import and export will go through this user's virtual machine. |
Dirsync operations are run automatically based on times specified during the configuration process. However, certain commands can be issued from the console or via the CP SMSG command once the Dir Sync machine is started.
IMPORT - The import command causes an immediate import operation to be performed. This operation will be successful only if the appropriate e-mail message has been sent from the central directory. | ||
EXPORT - The export command will cause an immediate export file to be created and sent as a message to the central directory defined in the configuration. | ||
QUIT - The quit command causes immediate termination of the service machine. To restart it, either issue the PROFILE command, or have the machine autologged. |
Alternatively, you can issue the CP SMSG IMPORT, CP SMSG EXPORT, or CP SMSG QUIT command from any virtual machine defined as an administrator in the CONFIG file.
OV/VM has a native facility which allows a user to enter a question mark in the To: field to get a list of users who can be selected as recipients of the note. This can be customized to use the dirsync directory as the default directory. Type the name of the desired directory in the PHONE DEFAULTS file located on the phone directory disk, usually, SYSADMIN 397.
Configuring the NJE/PROFS Client |
Note - Refer to Appendix A for more information on these configuration parameters.
1. | From OS/2, start the PC Clients Setup application. |
2. | Select NJE/PROFS and click Continue. |
3. | Enter the appropriate NJE/PROFS parameters. |
FIGURE 2-4 NJE/PROFS Parameters Screen
- Server TCP Port: This value should match the NJE server port specified using the Administration Console in the PROFS channel's Transport tab. The default value is 5109. This field specifies the IP port number on which the OS/2 listens.
- Local Node: This is the OS/2 NJE host name. This value should match the NJE host name specified using the Administration Console in the PROFS channel's Transport tab and columns 1-8 in the REMLOC file. For example, SUN1. In this field, enter the hostname of this machine that is recognized by the mainframe.
- Remote Node: The RSCS host name. This value should match the NJE peer name specified using the Administration Console in the PROFS channel's Transport tab (for example, PROFSSVR).
- Local LU Name: This value should match the LU Name size specified in the VTAM configuration file and RSCS configuration file. (for example, TBA1015).
- Remote LU Name: This value should match the RSCS applid specified in the RSCS configuration file and the NJE peer name specified using the Administration Console in the PROFS channel's Transport tab (for example, PROFSSVR).
- NJE Buffer Size: This value should match the NJE buffer size specified in the RSCS configuration file. The default value is 1024.
The NJE buffer size cannot be larger than the RU size. RU sizes are a pair of two-digit hexadecimal numbers that each represent an RU size, one for each direction of transfer. To convert between the two-digit hexadecimal RU sizes and the decimal numbers they represent, refer to the following table (see TABLE 2-2):TABLE 2-2 Hexadecimal RU Numbers to Decimal Numbers Conversion .
4. | Click OK to exit NJE/PROFS setup. |