Category : OS/2 Files
Archive   : OS2CMAPI.ZIP
Filename : APPC.ME

 
Output of file : APPC.ME contained in archive : OS2CMAPI.ZIP



Version 1.1 (c) Copyright International Business Machines Corp., 1988


APPC SAMPLE PROGRAM

The APPC sample programs are a sample of writing application programs
using the APPC interface verbs. The function of the sample programs is
to transmit any PC file from the server PC to the requester PC. To
support the function, there are two sample programs. One is a receive
program, which is referred as the requester side. The other is a send
program, which is referred as the server side. On the requester side,
a user starts the requester program, supplying a filename and path on
the OS/2 command prompt. The server transmits that file to the
requester in the directory defined by the path.

The sample programs are designed to work in the OS/2 protected mode,
with the Communications Manager of the OS/2 Extended Edition. The
sample program source code and the supporting files are for C, PASCAL,
and MASM languages.

RESTRICTIONS

1. When requesting a file with path, the directory must exist on both
the workstations.

2. When requesting a file without the path, the server assumes that
the file is in C:\CMLIB, since that is the environment inherited
by the server program, when the Communications Manager starts the
server program. The file is transmitted to the requester program
and is stored in the default directory. The default directory will
be the directory where the requester program resides.

PREREQUISITES

To run the sample program, a user must be familiar with the following
things:

1. OS/2 installation and command prompt

2. TOOLKIT installation

3. Communications Manager installation

4. Compiler of the language in which you are interested

INSTALLATION

Install IBM OS/2 Extended Edition Version 1.1 according to the
installation proceduere in the IBM Operating System/2 Extended
Edition Version 1.1 Getting Started book, install the Communications
Manager using prompted mode. The APPC feature group of the Communications
Manager needs to be installed. This will copy the APPC API structures
to the Communications Manager directory, which is C:\CMLIB.
Install the IBM OS/2 Toolkit Version 1.1 using its installation
proceduere.

1



Install the compiler of the language in which you are interested. Use
the installation procedure of the compiler. Refer to the following
language section for additional information.

NOTES

1. The instructions for typing at the OS/2 command prompt shows the
command line with the path for information only. For example,
[C:] is displayed, and you must not type it at the OS/2 command
prompt.

SUPPORTED LANGUAGES

1. C LANGUAGE

a. INSTALL C COMPILER

Install the IBM C/2 compiler Version 1.1 using the
installation procedure of the compiler. The INSTAID facility is
used to install the compiler. Have the master diskette of the
compiler in drive A, and type the following on the OS/2
command prompt:

[C:\]instaid a:C11.pip [Press Enter]

Follow the directions provided by the menus. Choose the
default directories and subdirectories. Choose "No" when
prompted whether to set up the environment immediately.
The compiler is installed at this point.

b. C SAMPLE PROGRAMS

There are two APPC sample programs. The requester side is
called FILECREQ. The server side is called FILECSVR. Copy the
files with the filename FILECREQ and FILECSVR into directory
C:\IBMC2. The files to be copied are Source code (.C extension),
Module definition (.DEF extension), Make file (no extension),
and Link response (.LRF extension). The Bind message file
(.BND extension) is to be copied later.

All the INCLUDE files are required in \IBMC2\INCLUDE directory.
Copy the files APPC_C.H and ACSSVCC.H from the Communications
Manager directory (C:\CMLIB) into the \IBMC2\INCLUDE directory.
Also copy DOSCALLS.H from C:\TOOLKT11\C\INCLUDE directory into
\IBMC2\INCLUDE directory.

c. LIBRARY FILES FOR C SAMPLE PROGRAM

All the LIBRARY files must reside in \IBMC2\LIB directory. Copy
ACS.LIB from the Communications Manager directory (CMLIB) into
the \IBMC2\LIB directory and DOSCALLS.LIB from the OS/2 directory
(OS2) into the \IBMC2\LIB directory.

2



d. COMPILE/LINK C SAMPLE PROGRAMS

During installation of the compiler, a file NEW-VARS.CMD is
created in your \IBMC2\BIN\SAMPLE directory. Change your current
directory to \IBMC2\BIN\SAMPLE. Type the following at the OS/2
command prompt to set up the environment for the compiler.

[C:\IBMC2\BIN\]new-vars [Press Enter]

Change your current directory to C:\IBMC2

To compile and link the requester program, type the following
at the OS/2 command prompt:

[C:\IBMC2]make filecreq /r [Press Enter]

To compile and link the server program, type the following on
the command line:

[C:\IBMC2]make filecsvr /r [Press Enter]

The files FILECREQ.EXE and FILECSVR.EXE will be created.

e. BIND MESSAGE FILES

You must have installed the TOOLKIT already to bind the
message files to the sample programs.

FILECREQ.EXE and FILECSVR.EXE files must be bound with the
APPC sample program message file. Copy the APPC message text
file APX.TXT into \TOOLKT11\BIN directory. Change the current
directory to \TOOLKT11\BIN, and then type the following on the
OS/2 command prompt:

[C:\TOOLKT11\BIN]mkmsgf apx.txt apx.msg [Press Enter]

A message file APX.MSG is created. This file must be bound
with the executable files. Copy the file FILECREQ.BND to the
\TOOLKT11\BIN directory.

To bind the message file with the requester program, type the
following on the OS/2 command prompt:

[C:\TOOLKT11\BIN]msgbind filecreq.bnd [Press Enter]

Message file for server program is not required to be bound,
since it uses the Communications Manager's Message Log
facility. Copy the file APX.MSG in the C:\CMLIB directory.

3



After the above procedure, the executable files FILECREQ.EXE
and FILECSVR.EXE are in directory C:\IBMC2 in executable form.

2. PASCAL LANGUAGE

a. INSTALL PASCAL COMPILER

Install the IBM PASCAL/2 compiler Version 1.0 using the
installation procedure of the compiler. The INSTAID facility is
used to install the compiler. Have the master diskette of the
compiler in drive A, and type the following on the OS/2
command prompt:

[C:\]instaid a:pascal.pip [Press Enter]

Follow the directions provided by the menus. Choose the
default directories and subdirectories. The compiler is
installed at this point.

b. PASCAL SAMPLE PROGRAMS

There are two APPC sample programs. The requester side is
called FILEPREQ. The server side is called FILEPSVR. Copy the
files with the filename FILEPREQ and FILEPSVR into directory
C:\PASCAL. The files to be copied are Source code (.PAS
extension), Module definition (.DEF extension), Make file (no
extension), and Link response (.LRF extension). The Bind
message files (.BND extension) are to be copied later.

All the INCLUDE files are required in \PASCAL\SRC directory.
Copy the files APPC_CON.INC, APPC_TYP.INC, APPC_EXT.INC,
ACSSVCP1.INC, ACSSVCP2.INC, and ACSSVCP3.INC from the
Communications Manager directory (C:\CMLIB) into the
\PASCAL\SRC directory.

c. LIBRARY FILES FOR PASCAL SAMPLE PROGRAM

All the LIBRARY files must reside in \PASCAL\LIB directory.
Copy ACS.LIB from the Communications Manager directory (CMLIB)
into the \PASCAL\LIB directory and DOSCALLS.LIB from the OS/2
directory (OS2) into the \PASCAL\LIB directory.

d. COMPILE/LINK PASCAL SAMPLE PROGRAMS

During installation of the compiler, a file PASCENVR.CMD is
created in your \PASCAL\BIN directory. Change your current
directory to \PASCAL\BIN. Type the following on the OS/2
command prompt to set up the environment for the compiler.

[C:\PASCAL\BIN]pascenvr [Press Enter]

Change your current directory to C:\PASCAL

4



To compile and link the requester program, type the following
at the OS/2 command prompt:

[C:\PASCAL]make filepreq [Press Enter]

To compile and link the server program, type the following at
the OS/2 command prompt:

[C:\PASCAL]make filepsvr [Press Enter]

The files FILEPREQ.EXE and FILEPSVR.EXE will be created.

e. BIND MESSAGE FILES

You must have installed the TOOLKIT already to bind the
message files to the sample programs.

FILEPREQ.EXE and FILEPSVR.EXE files must be bound with the
APPC sample program message file. Copy the APPC message text
file APX.TXT into \TOOLKT11\BIN directory. Change the current
directory to \TOOLKT11\BIN, and then type the following on the
OS/2 command prompt:

[C:\TOOLKT11\BIN]mkmsgf apx.txt apx.msg [Press Enter]

A message file APX.MSG is created. This file must be bound
with the executable files. Copy the files FILEPREQ.BND and
FILEPSVR.BND to the \TOOLKT11\BIN directory.

To bind the message file with the requester program, type the
following on the OS/2 command prompt:

[C:\TOOLKT11\BIN]msgbind filepreq.bnd [Press Enter]

To bind the message file with the server program, type the
following on the OS/2 command prompt:

[C:\TOOLKT11\BIN]msgbind filepsvr.bnd [Press Enter]

Copy the file APX.MSG in the C:\CMLIB directory, since it is
also used for logging the messages through the Communication's
Manager Message Log facility.

After the above procedure, the executable files FILEPREQ.EXE
and FILEPSVR.EXE are in directory C:\PASCAL in executable
form.

3. MACRO ASSEMBLER

5



a. INSTALL MACRO ASSEMBLER

Install the IBM Macro Assembler/2 version 1.0 using the
installation procedure of the assembler. The INSTAID facility
is used to install the assembler. Have the master diskette of
the assembler in drive A, and type the following on the OS/2
command prompt:

[C:\]instaid a:masm.pip [Press Enter]

Follow the directions provided by the menus. Choose the
default directories and subdirectories. The assembler is
installed at this point.

During installation of the assembler, directory \MASM\BIN is
created.

b. ASSEMBLER SAMPLE PROGRAMS

There are two APPC sample programs. The requester side is
called FILEMREQ. The server side is called FILEMSVR. Copy the
files with the filename FILEMREQ and FILEMSVR into directory
C:\MASM\BIN. The files to be copied are Source code (.ASM
extension), Module definition (.DEF extension), Make file (no
extension), and Link response (.LRF extension). The Bind
message file (.BND extension) is to be copied later.

All the INCLUDE files are required in \MASM\BIN directory.
Copy the files APPC_A.INC and ACSSVCA.INC from the
Communications Manager directory (C:\CMLIB) into \MASM\BIN
directory. Also copy SYSMAC.INC, DOSCALLS.INC, and
SUBCALLS.INC from C:\TOOLKT11\MASM\INCLUDE directory into
\MASM\BIN directory.

c. LIBRARY FILES FOR ASSEMBLER SAMPLE PROGRAM

All the LIBRARY files must reside in \MASM\BIN directory.
Copy ACS.LIB from the Communications Manager directory (CMLIB)
into the \MASM\BIN directory and DOSCALLS.LIB from the OS/2
directory (OS2) into the \MASM\BIN directory.

d. ASSEMBLE/LINK ASSEMBLER SAMPLE PROGRAMS

Change your current directory to C:\MASM\BIN.

To assemble and link the requester program, type the following
at the OS/2 command prompt:

[C:\MASM\BIN]make filemreq [Press Enter]

To assemble and link the server program, type the following at
the OS/2 command prompt:

6




[C:\MASM\BIN]make filemsvr [Press Enter]

The files FILEMREQ.EXE and FILEMSVR.EXE will be created.

e. BIND MESSAGE FILES

You must have installed the TOOLKIT already to bind the
message files to the sample programs.

FILEMREQ.EXE and FILEMSVR.EXE files must be bound with the
APPC sample program message file. Copy the APPC message text
file APX.TXT into \TOOLKT11\BIN directory. Change the current
directory to \TOOLKT11\BIN, and then type the following on the
OS/2 command prompt:

[C:\TOOLKT11\BIN]mkmsgf apx.txt apx.msg [Press Enter]

A message file APX.MSG is created. This file must be bound
with the executable files. Copy the file FILEMREQ.BND to the
\TOOLKT11\BIN directory.

To bind the message file with the requester program, type the
following on the OS/2 command prompt:

[C:\TOOLKT11\BIN]msgbind filemreq.bnd [Press Enter]

Message file for server program is not required to be bound,
since it uses the Communications Manager's Message Log
facility. Copy the file APX.MSG in the C:\CMLIB directory.

After the above procedure, the executable files FILEMREQ.EXE
and FILEMSVR.EXE are in directory C:\MASM\BIN in executable
form.

To run the APPC sample program, you have to go through the following
additional steps.

HARDWARE REQUIREMENTS

It is assumed that each machine (a) has one primary SDLC adapter, or
if you plan to use IBM Token-Ring, an IBM Token-Ring adapter,
(b) uses a modem eliminator, and (c) uses a non-switched connection.
If your machines are different from this, then you must select the
appropriate parameters on the Data Link Control Profiles and Partner
Logical Unit Profiles.

CONFIG.SYS CHANGES

If you plan to use SDLC DLC, the SDLC device driver is added to the
config.sys file by adding the following statement in the CONFIG.SYS file:

7



DEVICE=C:\CMLIB\SDLCDD.SYS

If you plan to use IBM Token-Ring Network DLC, the IBM Token-Ring Network
device driver is to be added to the config.sys file by adding following
statements in the CONFIG.SYS file:

Server Side:

DEVICE=C:\CMLIB\TRNETDD.SYS CFG=C:\CMLIB\APPCTRSR.CFG
RUN=C:\CMLIB\ACSTRSYS.EXE

Requestor Side:

DEVICE=C:\CMLIB\TRNETDD.SYS CFG=C:\CMLIB\APPCTRRQ.CFG
RUN=C:\CMLIB\ACSTRSYS.EXE

You must restart your system (Alt+Ctrl+Del) for changes to take effect.

CONFIGURATION STEPS FOR SAMPLE PROGRAMS TO USE SDLC DLC

Create a configuration file for the APPC sample programs using the
configuration functions in Communications Manager.

The following instructions will configure two OS/2 Extended Edition
machines to run the APPC sample programs. They guide you through the
configuration process, panel by panel, until complete.

On the PC that will run the requester side of the sample program, copy
the system-supplied configuration file, ACSCFG.CFG, to APPCSDRQ.CFG in
the C:\CMLIB directory.

On the PC that will run the server side of the sample program, copy
the system supplied configuration file, ACSCFG.CFG, to APPCSDSR.CFG in
the C:\CMLIB directory.

Start the Communications Manager for the requester side using APPCSDRQ
as the startup configuration file.

Start the Communications Manager for the server side using APPCSDSR as
the startup configuration file.

Beginning at the "Communications Manager Main Menu" follow the
instructions below.

Server PC Requester PC

Press F10 Press F10
Select "Advanced" from action bar Select "Advanced" from action bar
Select "Configuration" Select "Configuration"
Press Enter Press Enter


8



Select "Workstation profile Select "Workstation profile"
(and auto-start options)" (and auto-start options)"
Select "Change" Select "Change"
Specify "Machine type- Specify "Machine type-
model number" model number"
Specify "IBM plant of manufacture- Specify "IBM plant of manufacture-
machine sequence number" machine sequence number"
Press Enter Press Enter

Select "SNA feature profiles" Select "SNA feature profiles"
Select "SNA base profile" Select "SNA base profile"
Select "Change" Select "Change"
Select "Auto-activate..." Yes Select "Auto-activate..." No
Press Enter Press Enter

Select "Data Link Control (DLC) Select "Data Link Control (DLC)
profiles" profiles"
Select "SDLC" Select "SDLC"
Select "Number" Adapter 0 Select "Number" Adapter 0
Select "Operation" Create Select "Operation" Create
Press Enter Press Enter

Select "Load DLC" Yes Select "Load DLC" Yes
Select "Line type" Non-switched Select "Line type" Non-switched
Select "Link station role" Select "Link station role"
Negotiable Negotiable
Press Enter Press Enter
Press Enter Press Enter

Select "Logical unit (LU) profiles Select "Logical unit (LU) profiles
Select "Create" Select "Create"
Specify "Profile name" FILESVR Specify "Profile name" FILEREQ
Press Enter Press Enter
Specify "LU name" FILESVR Specify "LU name" FILEREQ
Press Enter Press Enter

Select "Partner logical unit Select "Partner logical unit
profiles profiles
Select "Create" Select "Create"
Specify "Profile name" FILEREQ Specify "Profile name" FILESVR
Press Enter Press Enter
Specify "Fully qualified partner Specify "Fully qualified partner
LU name" second field as LU name" second field as
FILEREQ FILESVR
(Leave first field blank) (Leave first field blank)
Specify "LU alias" FILESVR Specify "LU alias" FILEREQ
Select "DLC TYPE" SDLC Select "DLC TYPE" SDLC
Specify "Partner LU session limit" Specify "Partner LU session limit"
of 1 of 1
Press Enter Press Enter
Select "Adapter 0" Select "Adapter 0"
Select "Add" Select "Add"
Specify "Mode name" MODE1 Specify "Mode name" MODE1
Specify "Initial session limit" ISL Specify "Initial session limit" ISL
Press Enter Press Enter
Select "End" Select "End"


9



Select "Transmission service mode Select "Transmission service mode
profiles" profiles"
Select "Create" Select "Create"
Specify "Profile name" MODE1 Specify "Profile name" MODE1
Press Enter Press Enter
Specify "Maximum RU Size" 256 Specify "Maximum RU Size" 256
Press Enter Press Enter

Select "Initial session limit Select "Initial session limit
profiles" profiles"
Select "Create" Select "Create"
Specify "Profile name" ISL Specify "Profile name" ISL
Press Enter Press Enter
Specify "Minimum number of Specify "Minimum number of
contention contention
winners source" 0 winners source" 1
Specify "Minimum number of Specify "Minimum number of
contention contention
winners target" 0 winners target" 0
Specify "Number of automatically Specify "Number of automatically
activated sessions" 0 activated sessions" 1
Press Enter Press Enter

Select "Remotely attachable Press ESC
transaction program (TP)
profiles" Press F10
Select "Create" Select "Verify" from action bar
Specify "Profile name" FILEMSVR Select "Run verify"
Press Enter Press Enter
Specify "TP filespec" as
(See Note below) Press F10
Select "Sync level" Either Select "Exit" from action bar
Select "Conversation type" Mapped Select "Exit communication
Select "TP operation" Queued - configuration"
attach manager started
Press Enter
Specify "TP name" FILEMSVR
Press Enter
Specify "Queued allocates timeout" 05
Specify "TP receive timeout" 05
Press Enter

Press ESC

Press F10
Select "Verify" from action bar
Select "Run verify"
Press Enter


10



Press F10
Select "Exit" from action bar
Select "Exit communication
configuration"

Note: This is the fully qualified name of the server program.
For example,

C:\SAMPLE\FILECSVR.EXE for the C server program
C:\SAMPLE\FILEPSVR.EXE for the PASCAL server program
C:\SAMPLE\FILEMSVR.EXE for the MASM server program

You need to exit the Communications Manager.

CONFIGURATION STEPS FOR SAMPLE PROGRAMS TO USE IBM TOKEN-RING NETWORK
DLC

Create a configuration file for the APPC sample programs using the
configuration functions in Communications Manager.

The following instructions will configure two OS/2 Extended Edition
machines to run the APPC sample programs. They guide you through the
configuration process, panel by panel, until complete.

On the PC that will run the requester side of the sample program, copy
the system-supplied configuration file, ACSCFG.CFG, to APPCTRRQ.CFG in
the C:\CMLIB directory.

On the PC that will run the server side of the sample program, copy
the system supplied configuration file, ACSCFG.CFG, to APPCTRSR.CFG in
the C:\CMLIB directory.

Start the Communications Manager for the requester side using APPCTRRQ
as the startup configuration file.

Start the Communications Manager for the server side using APPCTRSR as
the startup configuration file.

Beginning at the "Communications Manager Main Menu" follow the
instructions below.

Server PC Requester PC

Press F10 Press F10
Select "Advanced" from action bar Select "Advanced" from action bar
Select "Configuration" Select "Configuration"
Press Enter Press Enter

11




Select "Workstation profile Select "Workstation profile"
(and auto-start options)" (and auto-start options)"
Select "Change" Select "Change"
Specify "Machine type- Specify "Machine type-
model number" model number"
Specify "IBM plant of manufacture- Specify "IBM plant of manufacture-
machine sequence number" machine sequence number"
Press Enter Press Enter

Select "SNA feature profiles" Select "SNA feature profiles"
Select "SNA base profile" Select "SNA base profile"
Select "Change" Select "Change"
Select "Auto-activate..." Yes Select "Auto-activate..." No
Press Enter Press Enter

Select "Data Link Control (DLC) Select "Data Link Control (DLC)
profiles" profiles"
Select "IBM Token-Ring Network" Select "IBM Token-Ring Network"
Select "Number" Adapter 0 Select "Number" Adapter 0
Select "Operation" Create Select "Operation" Create
Press Enter Press Enter

Select "Load DLC" Yes Select "Load DLC" Yes
Specify "Maximum RU size" 256 Specify "Maximum RU size" 256
Specify "Send Window Count" 4 Specify "Send Window Count" 4
Specify "Receive Window Count" 4 Specify "Receive Window Count" 4
Specify "C&SM LAN ID" Specify "C&SM LAN ID"
(See Note 1 below) (See Note 1 below)
Press Enter Press Enter

Select "Logical unit (LU) profiles Select "Logical unit (LU) profiles
Select "Create" Select "Create"
Specify "Profile name" FILESVR Specify "Profile name" FILEREQ
Press Enter Press Enter
Specify "LU name" FILESVR Specify "LU name" FILEREQ
Press Enter Press Enter

Select "Partner logical unit Select "Partner logical unit
profiles profiles
Select "Create" Select "Create"
Specify "Profile name" FILEREQ Specify "Profile name" FILESVR
Press Enter Press Enter
Specify "Fully qualified partner Specify "Fully qualified partner
LU name" second field as LU name" second field as
FILEREQ FILESVR
(Leave first field blank) (Leave first field blank)

12



Specify "LU alias" FILESVR Specify "LU alias" FILEREQ
Specify "Partner LU session limit" Specify "Partner LU session limit"
of 1 of 1
Select "Permanent Connection" Yes Select "Permanent Connection" Yes
Press Enter Press Enter
Select "Adapter 0" Select "Adapter 0"
Specify "Destination Address" as Specify "Destination Address" as
400000000002 400000000001
Press Enter Press Enter
Select "Add" Select "Add"
Specify "Mode name" MODE1 Specify "Mode name" MODE1
Specify "Initial session limit" ISL Specify "Initial session limit" ISL
Press Enter Press Enter
Select "End" Select "End"

Select "Transmission service mode Select "Transmission service mode
profiles" profiles"
Select "Create" Select "Create"
Specify "Profile name" MODE1 Specify "Profile name" MODE1
Press Enter Press Enter
Specify "Maximum RU size" 256 Specify "Maximum RU size" 256
Press Enter Press Enter

Select "Initial session limit Select "Initial session limit
profiles" profiles"
Select "Create" Select "Create"
Specify "Profile name" ISL Specify "Profile name" ISL
Press Enter Press Enter
Specify "Minimum number of Specify "Minimum number of
contention contention
winners source" 0 winners source" 1
Specify "Minimum number of Specify "Minimum number of
contention contention
winners target" 0 winners target" 0
Specify "Number of automatically Specify "Number of automatically
activated sessions" 0 activated sessions" 1
Press Enter Press Enter

Select "Remotely attachable Press ESC
transaction program (TP)
profiles" Select "Lan Feature Profiles"
Select "Create" Select "Change"
Specify "Profile name" FILEMSVR Press Enter
Press Enter Select "IBM Token Ring Network
Specify "TP filespec" as Adapter" (see note 3 below)
(See Note 2 below) Press Enter
Select "Sync level" Either Select "Universally Administered
Select "Conversation type" Mapped address" No
Select "TP operation" Queued - Press Enter
attach manager started Specify "Adapter Address" as
Press Enter 400000000002

13



Specify "TP name" FILEMSVR Press Enter
Press Enter Press Enter
Specify "Queued allocates timeout" Press ESC
05
Specify "TP receive timeout" 05 Press F10
Press Enter Select "Verify" from action bar
Select "Run verify"
Press ESC Press Enter

Select "Lan Feature Profiles" Press F10
Select "Change" Select "Exit" from action bar
Press Enter Select "Exit communication
Select "IBM Token Ring Network configuration"
Adapter" (see note 3 below)
Press Enter
Select "Universally Administered
address" No
Press Enter
Specify "Adapter Address" as
400000000001
Press Enter
Press Enter

Press ESC

Press F10
Select "Verify" from action bar
Select "Run verify"
Press Enter

Press F10
Select "Exit" from action bar
Select "Exit communication
configuration"

Note 1: Specify your LAN name or ID e.g. TRNET1

Note 2: This is the fully qualified name of the server program.
For example,

C:\SAMPLE\FILECSVR.EXE for the C server program
C:\SAMPLE\FILEPSVR.EXE for the PASCAL server program
C:\SAMPLE\FILEMSVR.EXE for the MASM server program

Note 3: Choose "IBM Token Ring Network Adapter" if you are using IBM
PC AT. If you are using a different machine or adapter choose
appropriate adapter, and refer to the "Systems Administrator's
Guide for Communications" for configuration help. Online help
is also available for each adapter.

You need to exit the Communications Manager.

RUNNING THE SAMPLE PROGRAMS

Create a new directory SAMPLE on the requester side workstation. Copy
the requester sample program (FILECREQ.EXE, FILEPREQ.EXE, or
FILEMREQ.EXE) to the SAMPLE directory.

14




Create a new directory SAMPLE on the server side workstation. Copy
the server sample program (FILECSVR.EXE, FILEPSVR.EXE, or
FILEMSVR.EXE) to the SAMPLE directory.

Start the requester side with the configuration file APPCSMPR. Start
the server side with the configuration file APPCSMPS. Start APPC on
both workstations by selecting "Start communications", then select
"APPC only".

Select Start Programs from the Task Manager screen and then select
OS/2 full screen command prompt on the requestor workstation.
Change the current directory to SAMPLE. Start your requester program
(FILECREQ.EXE, FILEPREQ.EXE, or FILEMREQ.EXE) with the path and
filename you want to request from the server program.
Remember that the directory you specify must exist on both
the systems. The specified file will be transmitted to the requester
workstation. The server system runs in unattended mode.












15


  3 Responses to “Category : OS/2 Files
Archive   : OS2CMAPI.ZIP
Filename : APPC.ME

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/