Sorry I omitted the meat of the program, but I initially was
looking for a starting point, even if that meant someone could clarify
what the message really meant. Let's be totally honest now. I mentioned
that I used the Xephon WAITREXX example as the basis of my program.
What I really mean is that I:
- Gutted it, reformatted, etc.
- The original WAITREXX consisted of the WAITREXX program that
ATTACHED a WAITTCB program to accomplish the STIMER
- I moved all my STIMER activity to the one program (ABRXCOMM) and
changed STIMER to STIMERM processing.
- Make us of a STIMER exit to post the completion.
- Expanded the options to be able to specify Bintvl, Dintvl, or Local
I thought the ATTACH method may have had something to do with the
problem so I created a 2 program scenario similiar to the original
WAITREXX, using a modified ABRXCOMM which I named ABRXWAIT. This
program then ATTACHed a ABRXWTCB for STIMER processing. Same results
after all the work. But this in itself could verify what you are saying
in that there is a bug in the ABRXCOMM program.
I guess what I am really looking for is an explanation of what is
going on. Following is the results I normally see with the problem I am
Time = 13:00:57
..OK Interval <=== NOTE - This is
what I get back from the function call ===>
Time = 13:01:00
IRX0812E Exec variables were being accessed while the exec was
23 +++ Command = ABRXWAIT('B',3000)
IRX0040I Error running CIBWAIT, line 23: Incorrect call to routine
To me I have been able to call the function and get information
returned. Most of the doc was straight forward in terms of storing some
value and it's length in the EVALBLOCK. I'm able to say the time which
means I am in REXX once again. Then I take off for the next function
call and the problem occurs.
- Can you expand on your "cleanup" reference in terms of REXX?
besides storing the return information?
- Is there something I need to do to some REXX control blocks on
- Are you thinking mainly standard linkage problems between the
function and REXX?
- Is there some doc that would better explain the message and
possibly give me some indications what would cause this sort of
I appreciate your response. You don't know how much searcing I'v
done trying to get some sor tof answer!