In the completion history, I found the message RB66512, “Submit error: Local member not found or system name problem.” What does this mean?
You will receive this error when Robot/SCHEDULE cannot locate a job it thinks it should have submitted. Often, this message is generated when a system name has changed, but Robot/SCHEDULE is not aware of the change. If a system name changes, you should run the command RBTSYSLIB/RSLCHGSYSN to ensure that all Robot product databases have the correct system name in them. If you have Robot/NETWORK on the system (even if you aren’t using it), you should also check for the existence of the the data area RBNCFG *DTAATPositions 5 – 12 of the data area should contain the current system name. If the information in this data area is incorrect, you should update it. You also can get more information from the message itself. Go to the Robot/SCHEDULE General System Defaults panel and make a note of the message queue that Robot/SCHEDULE sends messages to. Then find this same message in that queue. Display the message and press function key 1 to view extended message text. If these steps don’t resolve
Related Questions
- I receive the error message: problem java.io.inturruptedIO exception: local connection timed out. How do I get around this time out issue?
- What does it mean when I submit an order to the Online Trading system and receive a warning, error or order rejected message?
- What do I do if I receive an error message in the eLandings System and cannot submit my report?
