SAP Note 19584 - SAPcomm: getting the new version from SAPSERVx

Symptom:

New version of SAPcomm required.

Cause and prerequisites

Various program errors or new functions in SAPcomm.

Solution
The current versions of SAPcomm are stored on the servers 'sapservX' ('sapserv3'...'sapserv7') at SAP and can be downloaded from there via ftp.

Procedure:

1) Exit any 'old' versions of SAPcomm that are currently running
(with 'scmstop').

2) Save the current installation of SAPcomm. The download of the new
version only overwrites programs and grammar files - the SAPcomm
configuration (file sapcomm.cfg) is retained.

3) Change to the current directory.
SAPcomm under UNIX:
Change to the SAPcomm startup directory
(default: '/usr/sap/com/SYS/exe/run').
SAPcomm under OS/2:
Change to the SAPcomm root directory
(default: '\SAP\COM').

4) From this directory, start 'ftp'. Log on to your sapservX host and
change there to the /general/misc/sapcomm directory.
Go to the subdirectory for the newest version of SAPcomm, for
example 'rel31G'.
From here, go to the subdirectory that corresponds to the platform
where your SAPcomm is installed (or where you want to install it)
for example, 'AIX'.

5) Enter 'bin' to change the transfer mode to 'BINARY'.
Transfer the file in this directory using the ftp 'get' command.
After transferring this file successfully, quit FTP ('quit').

The procedure now depends on whether you are installing SAPcomm under UNIX or OS/2:

SAPcomm under UNIX:

6) The file you transferred is a compressed archive, that contains a
complete version of SAPcomm.
The name of the file is 'SAPcomm.tar.Z'.

7) Uncompress the file with the command:
uncompress SAPcomm.tar.Z
The directory should now contain the file SAPcomm.tar
(the original file SAPcomm.tar.Z is deleted).
Unpack the archive file with the following command:
tar -xvf SAPcomm.tar
The result should be a set of SAPcomm programs (executable files
with no extensions), SAPcomm grammar files (*.grm), configuration
examples ('*.cfg' and 'sapcomm.pfl'), as well as the SAPcomm API
files ('scmi.h','scmiux.o','scmitst.c').

8) Move the grammar files into the SAPcomm profile directory:
mv *.grm /usr/sap/com/SYS/profile
Move the non-program files into the SAPcomm directory for other
files (examples and SAPcomm API development):
mv *.* /usr/sap/com/etc

SAPcomm under OS/2:

6) The file you transferred is a self-expanding archive that contains
a complete version of SAPcomm.
The name of the file is 'SCMINST.EXE'.

7) Unpack the archive in the SAPcomm root directory by entering:
SCMINST -y
The result should be a set of SAPcomm programs (executable files
'*.exe'), dynamic libraries ('*.dll'), SAPcomm grammar files
('*.grm'), examples for configuration ('*.cfg' and 'sapcomm.pfl')
as well as the SAPcomm API files ('scmi.h','scmiux.o','scmitst.c').
These files are copied into the various directories, any existing
configuration file SAPCOMM.CFG is not overwritten.

8) Move all dynamic libraries from '\SAP\COM\SYS\EXE\RUN' into a
directory where the DLLs will be recognized when the program is
started, or include '\SAP\COM\SYS\EXE\RUN' in the 'SET LIBPATH'
statement in the 'CONFIG.SYS' file.

Additionally SAPcomm uses the dynamic libraries CPICS.DLL and
CPICT.DLL that are not contained in the archive SCMINST.EXE.
If these DLLs are not stored on your OS/2-PC, or if they are from
a lower release than the SAPcomm you just installed, you can also
get these DLLs via FTP. They are stored in uncompressed form in
the same directory as SAPcomm.

The last steps are the same for UNIX and OS/2:

9) Start the SAPcomm configuration compiler ('scmcfgcc'), in order to
set up your SAPcomm configuration for the new version.

10) Start the new SAPcomm version.

Additional key words

FTP, sapserv, sapcomm.cfg, SAPcomm.tar.Z, SCMINST.EXE