If Robot Schedule will not start, here are some things to check:

  • Check if the license code has expired. There will be a message in qsysopr message queue.

  • Find job logs from ROBOT and/or ROBOTREACT to see if errors occurred.

  • Check if the RBTSLEEPER job queue is on hold.

  • Verify RBTUSER and RBTADMIN user profiles are on the system. These two profiles need to be on the system in order for Robot Schedule to function correctly. The libraries must be deleted and restored after the profiles have been added to the system.

  • Are ROBOTLIB, QGPL or QTEMP libraries missing from Robot Schedule's job descriptions (SLEEPER, RBTBATCH, RBTOPALJD, ROBOTSBMJ, SLEEPSTART)?

  • Check for duplicate objects. RBTSLEEPER subsystem description may have been duplicated in a library ahead of RBTSYSLIB in QSYSLIBL.

  • Check QHST, see if there are any references to RBTSLEEPER ending or the jobs ROBOT or ROBOTREACT ending.

    *Were backups running?

    *Was RBT107 executed to end ROBOT and ROBOTREACT?

  • RBTSYSLIB is not in the system portion of the library list. Verify RBTSYSLIB is in the system value QSYSLIBL and try to start again. Note: Try removing RBTSYSLIB and re-adding it to QSYSLIBL. Under certain circumstances, the library shows in QSYSLIBL system value but may not be picked up by new jobs.

  • CPF1151 -'Library ROBOTLIB duplicated.' in RBT103 job. ROBOTLIB, QTEMP, or QGPL is in QSYSLIBL. All five job descriptions in ROBOTLIB need to be changed. Remove the duplicated library from the job description's library list. (When Robot Schedule is converted, the job descriptions will get changed back to our default and put ROBOTLIB, QTEMP and QGPL back in.)

  • ROBOTLIB is in the QSYSLIBL system value.

    Use the WRKSYSVAL SYSVAL(QSYSLIBL) to work with the system value. Use option 5 to display the system value and verify the library ROBOTLIB does indeed exist in the system value. If so, use option 2 to change the system value and remove ROBOTLIB from the list.

  • CPF1338 - 'Errors occurred on SBMJOB command.' from RBT1004. There would also be a duplicate library error in the job log. Or RPG0401 - ' The &1 &2 data area RBTWK was not found (C G S D F).'

    a) QTEMP, QGPL, or ROBOTLIB are in QSYSLIBL system value. All job descriptions in ROBOTLIB have these three libraries in their initial library list. Therefore the duplicate library has to be removed from QSYSLIBL. (WRKSYSVAL QSYSLIBL - 2 to change)


    b) The duplicate library has to be removed from all job descriptions in ROBOTLIB. [CHGJOBD (library/JOBD) INLLIBL(libraries)]. These job descriptions will have to be maintained any time a conversion is done on the product.

  • The message queue listed in the General System Defaults needs to be a valid message queue on the system.

  • Ensure there are no other IBM API's or commands in libraries ahead of QSYS (such as CRTDTAQ, CRTDTAARA)

  • If a conversion recently occurred and the user specified to NOT start Robot Schedule after the conversion, the Auto Start Job entry is removed from the RBTSLEEPER subsystem. This entry will have to be added back in manually.

  • Check the job log of the startup job ROBOTSTR. (The logging level in the job description RBTBATCH in ROBOTLIB may need to be changed to create full logging.) CHGJOBD JOBD(ROBOTLIB/RBTBATCH) LOG(4 00 *SECLVL) LOGCLPGM(*YES).


  • MCH1401 Receiving context contains duplicate object. STD8002 Your Robot Schedule license code is invalid. OS level is V4R5 that received this error. Try loading IBM PTF SF66664. If PTF does not work, call IBM. This is an IBM issue with MCH1401 error, Robot SCHEDULE cannot retrieve the license code, so product will not start.

  • Make sure that RBTUSER has *ALL authority to ROBOTLIB/SLEEPSTART and ROBOTLIB/RBTSBMJOB.

  • CPF9802 - not authorized to RBTUSER profile. Check the authority on RBTUSER and RBTADMIN user profiles.

    WRKOBJ xxxxx

Have you booked your annual Tech Update yet? Schedule one today.

Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case