Solving robot production incidents

This process is described for the operations team to know what main actions to carry out in order to solve MAPSROBOT robot production incidents.

Requirements: Know about System i, JOBD, JOBQ, SBS and CLASS.

How to know the name of the sub-system OPALE Server uses?

Select «MAPPING Operations menu» then in option 1 «MAPPING environment parameters», the name of the sub-system is displayed at the bottom right of the screen: SBS : MAPSROBOT

How to get information on jobd MAPDROBOT?

DSPJOBD MAP400/MAPDROBOT  (DSPJOBD JOBD(MAP400/MAPDROBOT)

User profile: MAPPING

Job queue: MAP400/MAPQROBOT

Request's data: CALL MAP_C812 '*YES'

Libraries: MAP400, QTEMP, QGPL

How to get information on MAPPING user batch?

DSPUSRPRF MAPPING

Messages queue: QUSRSYS/MAPPING

output queue: MAP400/MAPPING

Sub-system MAPSROBOT does not start anymore

Check that the MAPPING user is registered: WRKUSRPRF MAPPING

Check that user message queue exists: WRKMSGQ MAPPING

Check that MAPPING user queue exists: WRKOUTQ MAPPING

Check that MAP400 is not in the syslib: DSPSYSVAL QSYSLIBL

Check that the jobqs exist and are not being held: WRKJOBQ MAP400/MAPQ*

Check that the classes exist: WRKCLS MAP400/MAP_*

If it still does not work, run command:CHGJOBD MAP400/MAPDROBOT LOG(4 00 *SECLVL)

Then:

STRSBS MAP400/MAPSROBOT

Look for start-up log spool. The message has to be explicit. Apply necessary changes, then return to default configuration.CHGJOBD MAP400/MAPDROBOT LOG(0 99 *NOLIST)

The sub-system starts but spools are not processed

Check DTAQs jobs in MAPSROBOT. To do so, type command: WRKACTJOB SBS(MAPSROBOT)

You should see jobs with the same names as the DTAQs which were defined in the Mapping menu.

MAPSROBOT does not able DTAQs jobs to run

Check for DTAQs in the libraries.

To do so, in option 4 of the operations menu, check the name of DTAQs and their libraries (press F11) then check that the object exists:WRKOBJ « LIBNAME »/ « DTANAME »

MAPSROBOT runs jobs but files are not processed

Check that input OUTQs are linked to DTAQs.

To do so, in option 4 of the operations menu, check the name of input OUTQs and their libraries (press F11) then check that the data queue parameter corresponds to the DTAQ's name:CHGOUTQ « LIBNAME » / « OUTQNAME »

MAPSROBOT runs DTAQs jobs but they immediately stop

Step 1: Stop the robot using ENDSBS MAPSROBOT *IMMED

Step 2: Enter STRSBS MAPSOROBOT

Step 3: Enter DSPDTAQ « LIBNAME »/ « DTANAME »

If there is still this type of data: ENDRBTENDRBT, go back to step 1.

Note:

If you have created a new DTAQ in the robot without having stopped MAPSROBOT beforehand, then this is probably where the problem comes from. Indeed, new relationships can only be created if input OUTQs already use existing DTAQs. Otherwise, you need to stop and reboot the robot. Another possible reason would be a request to stop ENDRBT interrupted by a call system +2

A job is in MSGW but no information is found in the job's log

In the job options,

• Check the name of the JOBD used to submit the job. For instance MAPDSPEED then type: CHGJOBD MAP400/MAPDSPEED LOG(4 00 *SECLVL)
• Restart the job.
• Check the job's log and execute the following command.DSPJOBLOG (name of the job, user, job number)
• Then execute: CHGJOBD MAP400/MAPDROBOT LOG(0 99 *NOLIST)

Note:

Bien souvent l'erreur se situe sur l'utilisation du paramètre &CLSPLNUMS dans le robot. Si vous souhaitez le passer à un programme par un CALL d'un CL, il ne faut pas oublier de protéger ce paramètre par des simples cotes avant et après. Dans le cas contraire, l'iSeries va considérer ce paramètre comme une valeur numérique.

CALL MAP400/MONPGM PARM('&CLSPLNUMS')