OPALE - 10.0 - Utilisation - Utiliser le robot d'exploitation Mapping/en

Différence entre versions

De MappingDoc
 
(6 révisions intermédiaires par le même utilisateur non affichées)
Ligne 1 : Ligne 1 :
 
<languages/>
 
<languages/>
The robot is a sub-system of the software called MAPSROBOT. This robot listens to a specified DTAQ. The sub-system is launched by the Mapping user upon installation.  
+
The Robot is a sub-system called MAPSROBOT which listens to a specified DTAQ. The sub-system is launched by the Mapping user created during installation.  
  
The spooled files generated by the robot are generated by the owner of the original spooled file except if he does not have the right to submit a job (that is the case with QSECOFR rights)  
+
The spooled files generated by the robot are generated by the owner of the original spooled file except if he does not have the right to submit a job (as is the case with QSECOFR)  
  
 
If this is the case then Mapping is the owner of the new spooled file created by the robot.
 
If this is the case then Mapping is the owner of the new spooled file created by the robot.
  
The robot does not constantly analyse '''Outqs''', it only does so when a spooled file needs to be processed.
+
The robot does not listen to '''Outqs''' continuously and is active only when a spooled file needs to be processed.
  
  
 
===Defining input Outqs managed by the robot===
 
===Defining input Outqs managed by the robot===
  
All spooled files placed in Outqs will be processed by the robot. Input Outqs are linked to destination Outqs''' (where the remapped spooled files will be printed) and to a DTAQ. These relations are defined in Option 5 of the '''Operations Menu'''.
+
All the spooled files falling into the monitored Outqs will be processed by the robot. Input Outqs are linked to destination Outqs''' (where the remapped spooled files will be printed) and to a DTAQ. These relations are defined in Option 5 of the '''Operations Menu'''.
 
   
 
   
When a spooled file is placed in an original robot Outq in '''RDY''' status, a message is sent to the DTAQ, launching a job in the sub-system of the robot.
+
When a spooled file falls into an original robot Outq in '''RDY''' status, a message is sent to the DTAQ, launching a job in the robot's sub-system.
  
  
 
Caution:
 
Caution:
  
The spooled file needs to be placed in '''RDY state or the status needs to be changed''' if it is in HLD status. Otherwise no message will be sent to the DTAQ and the robot will not process the spooled file.
+
The spooled file needs to be in '''RDY status or released''' if it is in HLD status. Otherwise no message will be sent to the DTAQ and the robot will not process the spooled file.
  
 
In the PRTF, '''SCHEDULE''' parameter: the spooled file output (availability of the file set as a spooled file attribute) needs to be set to *FILEEND: The output spooled file is  
 
In the PRTF, '''SCHEDULE''' parameter: the spooled file output (availability of the file set as a spooled file attribute) needs to be set to *FILEEND: The output spooled file is  
  
available for editing as soon as the file is closed (and is not in *IMMED).
+
available for editing as soon as it is closed (and is not in *IMMED).
  
The robot processes the spooled file as soon as it is available. If it is in '''OPN''' status, the robot will work with the unfinished spooled file.
+
This is because the robot processes the spooled file as soon as it is available. If it is in '''OPN''' status, the robot would process an incomplete spooled file.

Version actuelle datée du 18 juin 2019 à 08:32

Autres langues :
English • ‎français

The Robot is a sub-system called MAPSROBOT which listens to a specified DTAQ. The sub-system is launched by the Mapping user created during installation.

The spooled files generated by the robot are generated by the owner of the original spooled file except if he does not have the right to submit a job (as is the case with QSECOFR)

If this is the case then Mapping is the owner of the new spooled file created by the robot.

The robot does not listen to Outqs continuously and is active only when a spooled file needs to be processed.


Defining input Outqs managed by the robot

All the spooled files falling into the monitored Outqs will be processed by the robot. Input Outqs are linked to destination Outqs (where the remapped spooled files will be printed) and to a DTAQ. These relations are defined in Option 5 of the Operations Menu.

When a spooled file falls into an original robot Outq in RDY status, a message is sent to the DTAQ, launching a job in the robot's sub-system.


Caution:

The spooled file needs to be in RDY status or released if it is in HLD status. Otherwise no message will be sent to the DTAQ and the robot will not process the spooled file.

In the PRTF, SCHEDULE parameter: the spooled file output (availability of the file set as a spooled file attribute) needs to be set to *FILEEND: The output spooled file is

available for editing as soon as it is closed (and is not in *IMMED).

This is because the robot processes the spooled file as soon as it is available. If it is in OPN status, the robot would process an incomplete spooled file.