I'm not quite sure just what the situation is. Could you post some code? What is the length of Time between Failure -- minutes, hours or what? Bobh
I'm not quite sure just what the situation is. Could you post some code? What is the length of Time between Failure -- minutes, hours or what? Bobh
It's not a matter of time it's a certain number of iterations. I haven't counted them exactly but I can run the functions and when the STDOUT file gets to a certain number of pages the error occurs. The number of pages depends on the trace and number of say staements we have in it to gather information. For a short term fix I am counting these iterations and "restarting" the function when it gets to 501. This avoids whatever is occuring. The REXX code calls RPG prgrams and 2 API's, QSNDDTAQ and QRCVDTAQ, the error manifests itself in errors when these are called, it can't find the Q's one time and a program the next. It seems at the moment that the string passed to the Command environment is bad or the command environment has a problem.
If you are dealing in REXX get a copy of REXXTRY running and type in say address() On the 400 this should return COMMAND If not, there is some other problem. bobh
I have already checked that using a say address throughout the code and it returns COMMAND with iteration right up to the failure. Thanks
could you post some of the code involved? bobh
I have to run some more tests using less complex code to isolate the problem. I will post the code at that time provided I ever get the chance to do it. In the meantime I have averted the issue by counting iterations and restarting the program at 500. thanks for your interest
Does the REXX program ever hit an EXIT command. bobh
yes in 2 conditional cases, there is a QRCVDTAQ that the program issues waiting for 15 minutes. If the 15 minutes passes without any entries being placed on the dtaq it will exit, this is done to close open files. After exiting the Rexx program is started again and waits for an entry on the same dtaq.The second case where it exits is from a Syntax error routine.
Does the REXX program have the statement: EXIT; in it. A rexx module has to end with either an EXIT or RETURN statement, else it gets tangled up bobh.
In both cases described an EXIT statement is used.What do you mean by "tangled" , can you provide any details ?Thanks