• Aucun résultat trouvé

Relationship between AS/400 and VTAM/NCP for a Leased Line 113

Dans le document A As/400, 5/38 AND (Page 134-140)

DEVICE DESCRIPTION (APPC)

VTAM/NCP BUILD MACRO BUILD NETID-USIBMRA

MAXSESS=15 VTAM/NCP LINE MACRO

RAOL9929 LINE ADDRESS(929,HALF)

VTAM/NCP PU MACRO

5.4 Section 1: Definitions on the PS/2 (RAOTPSCO)

In order to configure the PS/2 with AS/400 PC Support to connect it to the S/370 subarea network we must perform the following:

• Install PC Support on the AS/400

• Initialize PC Support code on the AS/400

• Install PC Support on the PS/2

• Modify the CONFIG.SYS file on the PS/2

• Modify the CONFIG.PCS file on the PS/2

• Check the STARTPCS.BAT file on the PS/2.

We used a PS/2 model 60 with an IBM Multi-Protocol Adapter/ A card to support the SOLC line 'Connection between the PS/2 and the S/370 subarea network.

5.4.1 Install PC Support on the AS/400

Sign on to the AS/400 as security officer (QSECOFR) to install AS/400 PC Support. See SC21-9765 AS/400 Licensed Programs Installation Guide for instal-lation instructions.

5.4.2 Initialize PC Support Code on the AS/400

You will have to run the CL command INZPCS in order to initialize AS/400 PC Support. All personal computers using PC Support need to have the same key-board type and code pages. If you enter the command with no parameters, it will take the default from the system.

5.4.3 Install PC Support on the PS/2

In the following installation description we assume that DOS 3.30 has already been installed on the PS/2.

Insert the AS/400 PC Support (PCS) diskette into drive A and type: A> INSTALL.

Install Exit

1

1. Work station emulation

1

I 2. Enhanced S2SG emulation 1

1 3. Token-ring 1

I> 4. SOLC 1

1---1

1 Esc=Cancel 1

*---*

n=Help

Before you install AS/4GG PC Support on your personal computer, ensure the AS/4GG and personal computer requi rements are comp'l ete I and you have obtained the required information to complete this installation program.

For more information, refer to the AS/4GG PC Support Installation Guide.

Figure 131. Installation Options Screen

Figure 131 is the screen that is displayed after you enter the INSTALL ( command. You will be installing the SOLC support so you will take option 4 on

the hardware options screen.

114

AS/400, S/38 and PS/2 as T2.1 Nodes in -a Subarea Network

Then the following screen will be displayed:

Installing AS/4a8 PC Support (SDLC)

Complete the following with the information from the form; press Enter • PCS directory drive

PC location name System name

Local station address Which functions wi 11 you use?

Enter Esc=Cancel F1KHelp F3~Exit

• (C)

(USIBHRA.RAOTPSCa) (RAOTNNB8) (C5) (a1 - FE)

.>Organizer

>Work Station Function

>Hessage Function

>Virtual Printer

Figure 132. Installing AS/400 PC Support (SOLC) Screen

After entering these values, the PCS directory is created in the disk drive C and the PC Support files are copied from the AS/400 PC Support diskette to this directory. At the same time the CONFIG.SYS file is modified and the files CONFIG.PCS and STARTPCS.BAT are created using the information you have just entered. For an explanation of the parameters see Figure 135 on

page 116.

Figure 133 displays the PCS directory when the installation is completed.

C:\PCS>dir

5.4.4 Modify the CONFIG.SYS File on the PS/2

The CONFIG.SYS file is the PS/2 configuration file and not an AS/400 PC Support file. If you already have this file on your PS/2, the installation program will automatically add the device drivers to be used by the PC Support memory manager and shared folders. If you are using the workstation function,

"files = 15" will be added to the CONFIG.SYS file. If you are using a token-ring attachment, the device drivers for the LAN adapter handler will be included in CONFIG.SYS file.

We also included F

=

10 to the ECYOOX driver which allows ten files to be opened at one time and B = 20 to the FSOD driver which sets aside twenty blocks (block size is 1880 bytes) of storage for cache buffering on the PS/2.

C>type CONFIG.SYS files=15

break=on lastdrive=Z

OEVICE=C:\PCS\EIMPCS.SYS OEVICE=C:\PCS\ECYOOX.SYS F=lO OEVICE=C:\PCS\FSOO.SYS B=20

Figure 134. CONFIG.SYS File Screen

5.4.5 Modify the CONFIG.PCS File on the PS/2

This file is the PC Support configuration file on the PS/2. It is created with the parameters you defined when you. installed PC Support on the PS/2. In Figure 135 you can see the default CONFIG.PCS file that was created.

C>cd pcs

C:\PCS>type CONFIG.PCS.

RTYP SOLC

RTLN USIBMRA.RAOTPSCO SOLI RAOTNNBO,C5

Figure 135. CONFIG.PCS Default File Screen

We will now tailor this CONFIG.PCS file to add in the parameters for the SOLC leased line connection to the S/370 subarea network.

In Figure 136 on page 117 the following parameters are defined:

• RTYP SDLC specifies the router to use when communicating with the AS/400 behind the S/370 subarea.

• RTLN USIBMRA.RAOTPSCO uniquely identifies the PS/2 to the network. The network identifier is USIBMRA and the PC location name is RAOTPSCO.

This name is sent to the AS/400 whenever the router makes contact and it must match the LU name in the NCP of the PS/2.

• SDLI RAOTNNBO,C5,RUSSELL specifies the link identification and must be in the CONFIG.PCS file when the IBM SOLC router is used. Link identifica-tion includes the system name (which must match the local locaidentifica-tion name on the AS/400 and the LU name in VTAM/NCP for the AS/400), local station

116

AS/400, S/38 and PS/2 as T2.1 Nodes in a Subarea Network

address (which must match the PU address in VTAM/NCP for the PS/2) and user 10 ( which must be a valid user profile on the AS/400).

• RTDN RAOTNNBO specifies the default system name used to start conversa-tions if a name is not used. In this case it is the AS/400 local location name.

• SDLT MP specifies that the line type is a nonswitched multi-point line. If you were using a leased line it would be NONSWPP.

• RTCU RUSSELL specifies the common user 10 to be used if it hasn't been defined on the AORS, EMU ot TRU identifiers. It also will be used when the user 10 is prompted by the start router command.

• SDDE YES specifies that NRZI data coding will be used. It must match with the NRZI parameter you defined in VTAM/NCP for this PS/2.

• SDMR FULL specifies that the line will operate at 1000/ 0 of the selected data rate on the modem if it supports the rate select feature.

• SDLF HALF specifies half duplex for the line. This means that the.

line/modem can't be used to transmit data in both directions at the same time. It is required to be HALF because we are using a multipoint line. The default for the SOMR identifier is HALF.

RTYP SOLC

RTLN USIBMRA.RAOTPSC8 SOLI RAOTNNB8,C5,RUSSELL RTDN RAOTNNB8

SOLT MP RTCU RUSSELL SOOE YES SOMR FULL SOLF HALF

Figure 136. Tailored CONFIG.PCS File for the PS/2 SOLC Link

5.4.6 Check the STARTPCS.BAT File on the PS/2

This file is created when you install PC Support on the PS/2. The contents will depend on the functions you selected in Figure 132 on page 115. This file will contain the necessary commands to start PC Support. You have the option to leave this file as created or to customize it for your specific requirements.

Details of this customization can be found in PC Support Operations Reference Manual. We recommend that you copy the contents of QIWSFLR to your fixed disk drive for performance reasons. Once that has been done you must change the STARTPCS.BAT file to run from the C drive.

The following screen displays the STARTPCS.BAT file.

C: \PCS\STARTRTR C: PCS\CONFIG.PCS ECHO OFF

C: \PCS\STARTMSG C: \PCS\CONFIG.PCS ECHO OFF

Figure 137. STARTPCS.BAT File

118 AS/400, S/38 and PS/2 as T2.1 Nodes in a Subarea Network

Start Message Function

Start Virtual Print Function

Start Workstation Function selected with one standard session

Start AS/400 PC Support

Organizer

Dans le document A As/400, 5/38 AND (Page 134-140)