I am a little curious about the Run Unit Details error message as follow:
6 MABP00000 Unresolved - No Entry Point Not found
This is trying to resolve mainframe programs (CICS)and it is complaining the Entry Point is not found. Typically the COBOL member name is up to 8 characters and I like to know how RAA is figuring MABP00000 (9 character entry point) is missing when it is not even referenced by the calling program.
The Entry Point to MABP0000 is parsed successfully and that is the program/run unit that is called. Where can I look to resolve this issue?
This topic has been locked.
3 replies Latest Post - 2012-12-18T23:03:01Z by jcdelmo
Pinned topic Run Unit Error Resolution
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-18T23:03:01Z at 2012-12-18T23:03:01Z by jcdelmo
hiroleen 270005GN8819 PostsACCEPTED ANSWER
Re: Run Unit Error Resolution2012-12-17T16:36:47Z in response to hiroleenI have done a little more research - there is a hard coded move of the program name from 14 byte long field to 8 byte long field. The 14 byte long field has 9 characters + spaces and when it is moved to 8 byte field, the extra character and spaces get truncated. The program transfer occurs from the 8-byte field.
RAA takes the moving field information to ascertain Run Unit rather than the moved field. I think this is my conclusion for the Run Unit error with 9 byte long program (run unit) name. Is this a fair assessment?
jcdelmo 0600012HN8341 PostsACCEPTED ANSWER
Re: Run Unit Error Resolution2012-12-18T23:03:01Z in response to hiroleenIs it true that the CALL is a dynamic one? That the data element being called is also used for other purposes than the CALL?
Could you send the program to firstname.lastname@example.org for analysis? I'd like to see if the dynamic data functionality can be refined, as RAA is designed to find CALLs from code like:
MOVE 'ABC0001' TO CALL-NAME CALL CALL-NAME