Our new E1 interface to Robot seems to have created an issue where previous EDI react jobs are not finishing in the OS and so Robot Schedule continues to think they are still running. After looking at the job log for the hung job I noticed it only created a data queue in the ROBOTLIB. I check this by entering WRKOBJ ROBOTLIB/RJ*. There are no more entries in the job log after “Object copied.” I know the job is running properly if a JDE job shows a data area being created. When I do an F1 on one of the “Object copied” messages in the job log it will show an error in the IFS entry.
Help Systems says that we are rolling job numbers since we rarely IPL or recycle the Robot products. I’ve started to recycle Robot every other week and the conflicts have diminished, but it still does happen. Has anyone had the same problem, and what did you do to correct it?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!