OPALE - 10.0 - Installation - Installation OPALE Server/en

Différence entre versions

De MappingDoc
(Page créée avec « By default during the installation process, the MAPPING user account is created with a blank password. »)
(Contenu remplacé par « . »)
 
(67 révisions intermédiaires par 3 utilisateurs non affichées)
Ligne 1 : Ligne 1 :
−
==Pré-requis==
+
<languages />
 +
==Requirements==
  
−
Ce guide décrit les procédures d’installation et de mise à jour du produit OPALE Server sur un système IBM i.  
+
This guide explains how to install and update OPALE Server on an IBM i server.  
  
−
Pour rappel, il est recommandé de mettre à jour les autres modules de la solution Mapping en même temps. Cela afin d'éviter toute erreur de compatibilité.
+
As a reminder, it is recommended to also update the other Mapping Suite software components at the same time to prevent errors due to version conflicts.
  
−
===Système===
+
===System===
  
−
Configuration minimale requise :
+
Minimum requirements:
  
−
*OS/400 V7R1 ou supérieur
+
*OS/400 V7R1 or higher
−
*2 Go d’espace disque
+
*2 Gb of free disk space
−
*Connexion FTP
+
*FTP connection
−
+
 
−
En cas de mise à jour de M-Processing Server :
+
In case of M-Processing Server update:
  
−
*Se référer au process d'upgrade/migration : [[OPALE:10.0:Migration:Process de migration|Process d'upgrade/Migration]]
+
*Please refer to the [[OPALE:10.0:Migration:Process de migration|Upgrade Process]].
  
−
Remarque : Sur OS/400 V7R1 et supérieur, les versions de M-Processing Server antérieures à la 7.1 ne sont pas compatibles avec Opale.
+
Note: On OS/400 V7R1 and higher, the versions of M-Processing Server older than 7.1 are not compatible.
  
−
===Sécurité===
+
===Security===
  
 
The <code>QSECOFR</code> profile is required to install the software.
 
The <code>QSECOFR</code> profile is required to install the software.
Ligne 45 : Ligne 46 :
 
====Transferring and creating content from the library====
 
====Transferring and creating content from the library====
  
−
There are 3 solutions
+
There are 3 solutions:
  
−
*Transferring the file <span style="background-color:rgba(0, 0, 255, 0.2);">MXXXXX.SAVF</span> via FTP to the previously created library. (Recommanded)
+
*Transferring the file <span style="background-color:rgba(0, 0, 255, 0.2);">MXXXXX.SAVF</span> via FTP to the previously created library (recommended).
 
*Transferring the file <span style="background-color:rgba(0, 0, 255, 0.2);">MXXXXX.SAVF</span> via SCP to the previously created library.
 
*Transferring the file <span style="background-color:rgba(0, 0, 255, 0.2);">MXXXXX.SAVF</span> via SCP to the previously created library.
  
−
However, it is also possible to transfer the ZIP archive and afterwards:
+
However, it is also possible to transfer the ZIP archive and then:
  
−
*to extract the archive directly from the previously created library.
+
*Extract the archive directly into the library created previously.
  
  
−
=====Transferring FTP from the SAVF to the IBM i system=====
+
=====Transferring the SAVF to the IBM i using FTP=====
  
 
Transferring the MXXXXX.SAVF to the created library.
 
Transferring the MXXXXX.SAVF to the created library.
Ligne 78 : Ligne 79 :
  
 
=====SSH Transfer to the IFS=====
 
=====SSH Transfer to the IFS=====
−
If the IBM has its SSH server configured.
+
If the IBM i has its SSH server configured.
  
 
Transfer the SAVF file (or the ZIP file) using the SCP protocol (e.g. using WinSCP) to a folder on the IFS.
 
Transfer the SAVF file (or the ZIP file) using the SCP protocol (e.g. using WinSCP) to a folder on the IFS.
Ligne 87 : Ligne 88 :
  
  
−
=====Extracting the SAVF from the IFS=====
+
=====Extracting the SAVF to the IFS=====
−
If the ZIP has been transfered to the AS, the <code>jar</code> tool allows you to unzip archives, under <code>qsh</code>.
+
If the ZIP archive has been transferred to the IBM i, you can use the <code>jar</code> tool to unzip it, under <code>qsh</code>.
  
 
The extracted file should be <span style="background-color:rgba(0, 0, 255, 0.2);">MXXXXX.SAVF</span> :
 
The extracted file should be <span style="background-color:rgba(0, 0, 255, 0.2);">MXXXXX.SAVF</span> :
Ligne 110 : Ligne 111 :
  
 
Enter the name of the library you want to install or update.<br />
 
Enter the name of the library you want to install or update.<br />
−
<u>Caution</u> : Whether this is a new install or an upgrade, do not use a production library. Please refer to the [[OPALE:10.0:Migration:Process de migration|Upgrade process]]
+
<u>Caution</u>: Whether this is a new install or an upgrade, do not use a production library. Please refer to the [[OPALE:10.0:Migration:Process de migration|Upgrade process]]
  
 
[[File:Install0.PNG|700px|none]]
 
[[File:Install0.PNG|700px|none]]
Ligne 117 : Ligne 118 :
 
You will need to specify the:
 
You will need to specify the:
  
−
*Sub-system name (the sub-system is created in the library where the product is restored)
+
*Sub-system name
 
*Installation folders
 
*Installation folders
 
*System LANGID and code page
 
*System LANGID and code page
Ligne 127 : Ligne 128 :
 
Note: The code page must always be 4 digits. Example 0037 or 0500.
 
Note: The code page must always be 4 digits. Example 0037 or 0500.
  
−
example of a code page: <br />
+
Sample code page: <br />
−
0297: French without the euro € symbol<br />
+
0297: French without Euro € symbol<br />
−
1147: French with the Euro € symbol <br />
+
1147: French with Euro € symbol <br />
  
−
After that if you are installing the product, you will need to [[OPALE:10.0:Saisie_de_la_clef_logicielle|enter the software activation codes called software keys]]. If you do not do it now, you can do it later by running the '''MAPKEY''' command. See Software Activation. If you are updating the product or do not have the software activation keys now, press <kbd>F3</kbd> to skip.
+
After that if you are installing the product, you will need to [[OPALE:10.0:Saisie_de_la_clef_logicielle|enter the software activation codes called software keys]]. If you skip this step, you can do it later by running the '''MAPKEY''' command. See Software Activation. If you are updating the product or do not have the software activation keys now, press <kbd>F3</kbd> to skip.
  
  
−
[[File:Activ1-2.PNG|700px|none]]
+
[[File:OP_S_MAPKEY_EN.JPG|700px|none]]
  
  
Ligne 140 : Ligne 141 :
 
   
 
   
  
−
[[File:Install param env.PNG|700px|none]]
+
[[File:OP_S_environment_en.JPG|700px|none]]
  
  
 
Note: After installing and before using the product, you will need to end the session and sign back in.
 
Note: After installing and before using the product, you will need to end the session and sign back in.
  
−
===Langage===
+
===Language===
−
====Selecting the language in the mapping menu====
+
====Selecting the language in the Mapping menu====
  
 
The screens of the Mapping menu can be displayed in the following languages:
 
The screens of the Mapping menu can be displayed in the following languages:
Ligne 156 : Ligne 157 :
 
The language is specified in the environment settings (Language File + Language ID).  
 
The language is specified in the environment settings (Language File + Language ID).  
  
−
Menu Mapping (enter the command <code>GO MAPPING</code>), option <kbd>14</kbd> then option <kbd>1</kbd>.
+
Mapping Menu (enter the command <code>GO MAPPING</code>), choose Option <kbd>14</kbd> then Option <kbd>1</kbd>.
−
or from the general Mapping menu: Operations menu / General Parameters
+
or from the general Mapping menu: Operations menu / Mapping Environment Settings
  
−
Otherwise, from the OPALE menu, choose Operations and then "Mapping Environment Parameters"
+
Otherwise, from the OPALE menu, choose Operations and then "Mapping Environment Settings"
  
−
[[File:Param lang.PNG|600px|none]]
+
[[File:OP_S_param_envir.JPG|700px|none]]
 
 
 
 
−
[[File:Langopale.PNG|600px|none]]
+
[[File:OP_S_environment_lang_en.jpg|700px|none]]
  
 
====Code pages====
 
====Code pages====
Ligne 464 : Ligne 465 :
 
|}
 
|}
  
−
==Software activation==
+
==Software Activation==
  
 
After installing the software, you will need to enter activation codes called licence keys. The licence keys are hardware-dependent. To obtain the licence keys for your system, you will need to:
 
After installing the software, you will need to enter activation codes called licence keys. The licence keys are hardware-dependent. To obtain the licence keys for your system, you will need to:
  
 
*Retrieve the system id
 
*Retrieve the system id
−
*Contact Technical Support, or log on to http://server.mappingsuite.com
+
*Contact Technical Support, or log on to https://server.mappingsuite.com
  
 
Note: If the licence keys are not entered, some screens in the Mapping menu cannot be accessed.
 
Note: If the licence keys are not entered, some screens in the Mapping menu cannot be accessed.
Ligne 483 : Ligne 484 :
 
*Processor Type
 
*Processor Type
  
−
[[File:Activ-infos.PNG|600px|none]]
+
[[File:OP_S_MAPKEY_EN.JPG|700px|none]]
  
−
===Entering the licence keys===
+
===Entering licence keys===
  
 
The number of licence keys required depends on the options purchased.
 
The number of licence keys required depends on the options purchased.
Ligne 491 : Ligne 492 :
 
For each key, run the <code>MAPKEY</code> command and [[OPALE:10.0:Saisie_de_la_clef_logicielle|enter the product number associated with the key]], and then press <kbd>Enter</kbd> to save.  
 
For each key, run the <code>MAPKEY</code> command and [[OPALE:10.0:Saisie_de_la_clef_logicielle|enter the product number associated with the key]], and then press <kbd>Enter</kbd> to save.  
  
−
[[File:Activ1-3.PNG|600px|none]]
+
.
  
  
−
Note: If the key you have entered is correct, the next screen is displayed. Otherwise, the key is highlighted as shown below.
+
Note: If the key you have entered is correct, the screen above is displayed and there is no confirmation message. If not, the key is highlighted as shown below but there is no error message.
  
 
[[File:Erroroactivation.PNG|600px|none]]
 
[[File:Erroroactivation.PNG|600px|none]]
Ligne 504 : Ligne 505 :
 
Just follow each step as explained. All checkpoints are listed to ensure that you can use the software as intended.
 
Just follow each step as explained. All checkpoints are listed to ensure that you can use the software as intended.
  
−
===Activatig the MAPPING user account===
+
===Activating the MAPPING user account===
  
 
The first thing you want to do is to activate the MAPPING user account on the system.
 
The first thing you want to do is to activate the MAPPING user account on the system.
Ligne 510 : Ligne 511 :
 
By default during the installation process, the MAPPING user account is created with a blank password.
 
By default during the installation process, the MAPPING user account is created with a blank password.
  
−
Exécuter la commande <code>CHGUSRPRF</code> pour définir un mot de passe pour l’utilisateur MAPPING.
+
Run the <code>CHGUSRPRF</code> command to set a password for the MAPPING user account.
  
−
Si cela n’est pas fait, vous ne pourrez pas utiliser ce profil à des fins de test.
+
If you skip this step, you will not be able to use this user account for test purposes.
  
−
Ce profil a toutes les autorisations nécessaires à l’utilisation du logiciel MAPPING. Il s’agit d’un profil de type <code>*PGMR</code> qui peut être utilisé comme bon vous semble si nécessaire.
+
The MAPPING user account has all the permissions needed to use the MAPPING software. It’s an account of type <code>*PGMR</code> that can be used as you see fit, if necessary.
  
−
===Vérification de l’environnement MAPPING===
+
===Checking the MAPPING environment===
  
−
Sur la ligne de commande, taper <code>MAPPING</code> pour accéder au menu principal.
+
On the command line, type <code>MAPPING</code> to open the main menu.
  
−
Sélectionner l’option "Paramètres d'environnement Mapping" dans le menu Exploitation.
+
Select option "Mapping Environment Settings" from the Operations menu.
  
−
Les chemins sont affichés en bas de l’écran et les valeurs dépendent du langage système (les valeurs peuvent changer selon le système sur lequel le logiciel est installé).
+
The paths are displayed in the lower end of the screen and the values depend on the system's language. The values may vary with the system on which the software is installed.
  
−
===Vérification de l’IFS===
+
===Checking the IFS===
  
−
Il est aussi recommandé de vérifier l’IFS lui-même. La façon la plus rapide de faire cela est d’utiliser la commande WRKLNK.  
+
It is also recommended that you check the IFS. The easiest way to do this is to run the WRKLNK command.
−
Dans tous les cas, les dossiers suivants doivent être présents dans l’IFS : mapout, mapping, mapreport, mapsend.
+
In any case, the following folders should be found in the IFS: mapout, mapping, mapreport, mapsend.
  
−
===Objets système requis par le logiciel MAPPING===
+
===System objects required by MAPPING software===
  
−
Pour approfondir le diagnostic, il faudrait vérifier les Job Queues et les Job Descriptions. Utiliser la commande WRKOBJ pour afficher les objets MAP* requis par le logiciel.
+
Another thing you might want to do is check the Job Queues and Job Descriptions required for use with Mapping. Run the WRKOBJ command to list MAP* objects required by the software.
  
−
Les Job Queues suivantes doivent apparaitre :  
+
The following Job Queues are required:
 
  MAPQFIND, MAPQMIDDLE, MAPQROBOT, MAPQSLOW, MAPQSMTP, MAPQSMTP2, MAPQSPEED, MAPQTCPIP
 
  MAPQFIND, MAPQMIDDLE, MAPQROBOT, MAPQSLOW, MAPQSMTP, MAPQSMTP2, MAPQSPEED, MAPQTCPIP
  
−
Les Job Descriptions suivantes doivent apparaitre :  
+
The following Job Descriptions are required:
−
MAPDFIND, MAPDMIDDLE, MAPDROBOT, MAPDSLOW, MAPDSMTP, MAPDSMTP2, MAPDSPEED, MAPDTCPIP
+
MAPDFIND, MAPDMIDDLE, MAPDROBOT, MAPDSLOW, MAPDSMTP, MAPDSMTP2, MAPDSPEED, MAPDTCPIP
  
−
===Démarrage du Robot===
+
===Starting the Robot===
  
−
Démarrer le robot à l’aide de la commande <code>STRRBT</code>, puis afficher le sous-système à l’aide de la commande <code>WRKSBS</code>.
+
Run the <code>STRRBT</code> command to start the robot, and then run the <code>WRKSBS</code> command to show the sub-system.

Version actuelle datée du 6 juin 2019 à 12:27

Autres langues :
English • ‎français

Requirements

This guide explains how to install and update OPALE Server on an IBM i server.

As a reminder, it is recommended to also update the other Mapping Suite software components at the same time to prevent errors due to version conflicts.

System

Minimum requirements:

  • OS/400 V7R1 or higher
  • 2 Gb of free disk space
  • FTP connection

In case of M-Processing Server update:

Note: On OS/400 V7R1 and higher, the versions of M-Processing Server older than 7.1 are not compatible.

Security

The QSECOFR profile is required to install the software.

Update or installation procedure

Update information

Please refer to the : Upgrade Process

Preparation

The software installation program can be downloaded from the Mapping Suite technical server at https://server.mappingsuite.com.

It is called setup_Opale_vXX.X.X.XXXXX.zip.

After downloading and uncompressing, it can safely be renamed to MXXXXX.SAVF.

Installing or updating by FTP

Creating the restore SAVF

Run this command: 

CRTSAVF FILE(QGPL/MXXXXX)

Transferring and creating content from the library

There are 3 solutions:

  • Transferring the file MXXXXX.SAVF via FTP to the previously created library (recommended).
  • Transferring the file MXXXXX.SAVF via SCP to the previously created library.

However, it is also possible to transfer the ZIP archive and then:

  • Extract the archive directly into the library created previously.


Transferring the SAVF to the IBM i using FTP

Transferring the MXXXXX.SAVF to the created library.

  • Under Windows in Start/Programs, choose MS-DOS Command Prompt
  • Go to the folder where the file you have just downloaded is saved e.g. CD My documents\Mapping
  • Enter ftp "AS400 IP address" (no quotes) e.g. ftp 9.5.5.3
  • And then sign in on the IBM i
  • Enter binary
  • Enter cd qgpl (or the library of the savf file you have created)
  • Enter put MXXXXX.savf
  • … (the file is being transferred and then you regain control)
  • Enter close
  • Then quit
  • And then exit


Cmdftp.PNG


Then, skip to Restoring the SAVF.

SSH Transfer to the IFS

If the IBM i has its SSH server configured.

Transfer the SAVF file (or the ZIP file) using the SCP protocol (e.g. using WinSCP) to a folder on the IFS. 

scp MXXXXX.SAVF user@as400:/QSYS.LIB/QGPL.LIB

Then, skip to Restoring the SAVF.


Extracting the SAVF to the IFS

If the ZIP archive has been transferred to the IBM i, you can use the jar tool to unzip it, under qsh.

The extracted file should be MXXXXX.SAVF : 

jar xf setup_Opale_server_v10.0.2.XXXXX.zip
cp MXXXXX.SAVF /QSYS.LIB/QGPL.LIB/MXXXXX.FILE

Then skip to Restoring the SAVF.

Restoring the SAVF

Run this command: 

RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(QGPL/MXXXXX)

Launch the installation script

Run this command: 

CALL PGM(QTEMP/RUNSETUP)

Installation steps

Enter the name of the library you want to install or update.
Caution: Whether this is a new install or an upgrade, do not use a production library. Please refer to the Upgrade process

Install0.PNG


You will need to specify the:

  • Sub-system name
  • Installation folders
  • System LANGID and code page


Install1.PNG


Note: The code page must always be 4 digits. Example 0037 or 0500.

Sample code page:
0297: French without Euro € symbol
1147: French with Euro € symbol

After that if you are installing the product, you will need to enter the software activation codes called software keys. If you skip this step, you can do it later by running the MAPKEY command. See Software Activation. If you are updating the product or do not have the software activation keys now, press F3 to skip.


OP S MAPKEY EN.JPG


Installation is complete when the following screen is displayed. Press Enter to continue.


OP S environment en.JPG


Note: After installing and before using the product, you will need to end the session and sign back in.

Language

Selecting the language in the Mapping menu

The screens of the Mapping menu can be displayed in the following languages:

  • French: MAPMSGFRA
  • English: MAPMSGENU
  • Japanese: MAPMSGJPN

The language is specified in the environment settings (Language File + Language ID).

Mapping Menu (enter the command GO MAPPING), choose Option 14 then Option 1. or from the general Mapping menu: Operations menu / Mapping Environment Settings

Otherwise, from the OPALE menu, choose Operations and then "Mapping Environment Settings"

OP S param envir.JPG

 

OP S environment lang en.jpg

Code pages

Supported code pages
Code Codepage ISO Nom Fichier
AFR (037) {latin1:1252} Afrikaans [Q037_19U-Q19U_037]
BEL (1025,1154) {Russian:1251} Byelorussian [Q1154_9R-Q9R-1154]
BGR (1025,1154) {Russian:1251} Bulgarian [Q1154_9R-Q9R-1154]
CSY (0870,1153) {latin2:1250} Czech [Q1153_9E-Q9E_1153]
DES (0500) {latin1:1252} Swiss German [Q1141_19U-Q19U_1141]
DEU (0273,1141) {latin1:1252} German [Q1141_19U-Q19U_1141]
CHS {0836} {s.chinese:00935} Simplified Chinese [Q013_19U-Q19U_037- S_Chinese_base1993.tbl]
CHT {0037} {t.chinese:00937} Traditional Chinese [Q013_19U-Q19U_037- T_Chinese_base1999.tbl]
ELL (0875) {Greek:1253} Greek [Q875_9G-Q9G_875]
ENA (037) {latin1:1252} Australian English [Q037_19U-Q19U_037]
ENG (0285,1146) {latin1:1252} United Kingdom English [Q285_19U-Q19U_285]
ENP (037) {latin1:1252} Uppercase English [Q037_19U-Q19U_037]
ENU (037) {latin1:1252} United States English [Q037_19U-Q19U_037]
ESP (0284,1145) {latin1:1252} Spanish [Q1145_19U-Q19U_1145]
FRA (0297,1147) {latin1:1252} French [Q1147_19U-Q19U_1147]
FRB (0500,1148) {latin1:1252} Belgian French [Q1148_19U-Q19U_1148]
FRC (0500) {latin1:1252} Canadian French [Q1148_19U-Q19U_1148]
FRS (0500) {latin1:1252} Swiss French [Q1148_19U-Q19U_1148]
GAE (0285,1146) {latin1:1252} Irish Gaelic [Q285_19U-Q19U_285]
HRV (0870,1153) {latin2:1250} Croatian [Q1153_9E-Q9E_1153]
HUN (0870,1153) {latin2:1250} Hungarian [Q1153_9E-Q9E_1153]
ITA (0280,1144) {latin1:1252} Italian [Q1144_19U-Q19U_1144]
ITS (0500) {latin1:1252} Swiss Italian [Q1148_19U-Q19U_1148]
JPN {0290} {Japanese:05026} Japanese Katakana [Q013_19U-Q19U_037- Japanese_base1996.tbl]
KOR {0833} {Korean:00933} Korean [Q013_19U-Q19U_037- Korean_base1992.tbl]
MKD (1025,1154) {Russian:1251} Macedonian [Q1154_9R-Q9R-1154]
NLB (0500,1148) {latin1:1252) Belgian Dutch [Q1148_19U-Q19U_1148]
NLD (037,1140) {latin1:1252} Dutch [Q037_19U-Q19U_037]
PLK (0870,1153) {latin2:1250} Polish [Q1153_9E-Q9E_1153]
PTB (037) {latin1:1252} Brazilian Portuguese [Q037_19U-Q19U_037]
PTG (037,1140) {latin1:1252} Portuguese [Q037_19U-Q19U_037]
ROM (0870,1153) {latin2:1250} Romanian [Q1153_9E-Q9E_1153]
RUS (1025,1154) {Russian:1251} Russian [Q1154_9R-Q9R_1154]
SKY (0870,1153) {latin2:1250} Slovakian [Q1153_9E-Q9E_1153]
SLO (0870,1153) {latin2:1250} Slovenian [Q1153_9E-Q9E_1153]
SQI (0500) {latin1:1252} Albanian [Q1148_19U-Q19U_1148]
SRB (1025,1154) {Russian:1251} Serbian Cyrillic [Q1154_9R-Q9R-1154]
SRL (0870,1153) {latin2:1250} Serbian Latin [Q1153_9E-Q9E_1153]
TRK (1026,1155) {Turkish:1254} Turkish [Q1155_5T-Q5T_1155]
THA {0838} {Thai :874} Thai [Q838_0T-Q0T_383]


Unsupported code pages
Code Codepage Nom
ARA 0420 Arabic
CAT 0284 Catalan
DAN 0277 Danish
FAR 1097 Farsi
FIN 0278 Finnish
HEB 0424 None Hebrew
ISL 0871 1149 Icelandic
NON 0277 Norwegian Nynorsk
NOR 0277 Norwegian Bokmal
SVE 0278 Swedish

Software Activation

After installing the software, you will need to enter activation codes called licence keys. The licence keys are hardware-dependent. To obtain the licence keys for your system, you will need to:

Note: If the licence keys are not entered, some screens in the Mapping menu cannot be accessed.

Server ID

Run the MAPKEY command to retrieve the information needed to generate your licence keys.

Write down the information below and then press F3 to exit.

  • Serial Number
  • Model Number
  • Processor Type
OP S MAPKEY EN.JPG

Entering licence keys

The number of licence keys required depends on the options purchased.

For each key, run the MAPKEY command and enter the product number associated with the key, and then press Enter to save.

.


Note: If the key you have entered is correct, the screen above is displayed and there is no confirmation message. If not, the key is highlighted as shown below but there is no error message.

Erroroactivation.PNG

Post-Installation checklist

This section is designed to help you check that the installation process was successful, and that the Mapping environment is configured correctly.

Just follow each step as explained. All checkpoints are listed to ensure that you can use the software as intended.

Activating the MAPPING user account

The first thing you want to do is to activate the MAPPING user account on the system.

By default during the installation process, the MAPPING user account is created with a blank password.

Run the CHGUSRPRF command to set a password for the MAPPING user account.

If you skip this step, you will not be able to use this user account for test purposes.

The MAPPING user account has all the permissions needed to use the MAPPING software. It’s an account of type *PGMR that can be used as you see fit, if necessary.

Checking the MAPPING environment

On the command line, type MAPPING to open the main menu.

Select option "Mapping Environment Settings" from the Operations menu.

The paths are displayed in the lower end of the screen and the values depend on the system's language. The values may vary with the system on which the software is installed.

Checking the IFS

It is also recommended that you check the IFS. The easiest way to do this is to run the WRKLNK command. In any case, the following folders should be found in the IFS: mapout, mapping, mapreport, mapsend.

System objects required by MAPPING software

Another thing you might want to do is check the Job Queues and Job Descriptions required for use with Mapping. Run the WRKOBJ command to list MAP* objects required by the software.

The following Job Queues are required: 

MAPQFIND, MAPQMIDDLE, MAPQROBOT, MAPQSLOW, MAPQSMTP, MAPQSMTP2, MAPQSPEED, MAPQTCPIP

The following Job Descriptions are required: MAPDFIND, MAPDMIDDLE, MAPDROBOT, MAPDSLOW, MAPDSMTP, MAPDSMTP2, MAPDSPEED, MAPDTCPIP

Starting the Robot

Run the STRRBT command to start the robot, and then run the WRKSBS command to show the sub-system.

Récupérée de « https://docs.mappingsuite.com/w/index.php?title=OPALE:10.0:Installation:Installation_OPALE_Server/en&oldid=13054 »
  • Powered by MediaWiki