Ansicht
Dokumentation

Addition to installation guidelines
Tip-No.: 2176 ( INFO2176 )

Short text

Addition to installation guidelines
Tip-No.: 2176

Symptom

The guidelines are not always correct.

Cause

It is not easy to keep a guideline that is produced every three
weeks current.

Solution

We suggest entering all new additions to the guidelines in a certain
note. The installer should then print this note before going
to the customer.

1. Timeout with self-defined objects.
For some computers (that are not so fast), parameter
rdisp/max_wprun_time must be xset to 0 so that the self-defined
object runs to completion. Reset to the old value after put|||

2. Error during import of self-defined objects.
Unfortunately, many errors that must be ignored still occur in the log
for the import of the self-defined objects. As long as the log ends
with a "summary", the installer must treat the object in question as
successfully completed.

3. Deleting old PUT directories.
You may delete ond PUT directories at the customers (create space||).

4. ||||| OS/2 graphics installation |||||||||||||||||||||||||||||||
Due to an error in the installation procedure for the SAP PC programs,
the paths in the configuration file for graphics (SAPGRAPH.INI) are not
adatped to the actual paths in the current installation.

Consequence: error no. 3 from the graphic multiplexer, which does not
find the graphics files.

Solution: rename or delete SAPGRAPH.INI, which is normally located
in directory SAPTEMU in directory GRAPH_P.

Graphics runs with default values without the configuration file, too,
if environment entry 'SAPGRAPH' shows the directory with the graphics
programs.
Check with:
>SET
set with:
>SET SAPGRAPH=correct_path/SAPGRAPH.INI
This entry is set correctly by the installation routine, however.

Additional info:
For all problems with the graphics, first attempt to start locally.
To do this, go to the directory with the graphics files and enter e.g.
>Gbusg -F Gbusg.DAT
you should see a picture of Mount St. Helens (before eruption).
This local test is possible for all .EXEs for which a .DAT of the
same name exists.

6. The definition of printer hp2564b appears to be destroyed by
the put. We do not yet have solution for this. You might print
the correct definition in S11 and adapt it at the customer's after
the put.

7. If problems with upper and lower-case writing appear in rdddic10:
se38
Program ....... rdddic10
Click program in the menu bar
Click generate
It should then work.