Debugging program called via WINEXEC

Question

We are upgrading from RM/COBOL v10.1 to v12.17 and Windows 7 to 10. This functionality worked prior to the upgrade.

I have a pair of program that I need to debug. I've compiled both with debugging on.

Program A calls program B using WINEXEC:

40920 STRING '"' DELIMITED BY SIZE
40920 RMCOBOL-PATH(1:PATH-INDEX) DELIMITED BY SIZE
40920 '\RUNCOBOL.EXE" B A="A' DELIMITED BY SIZE
40920 PNF-EMPLOYEE-ID DELIMITED BY SIZE
40920 PNF-FAMILY-MEMBER-ID DELIMITED BY SIZE
40920 '" L=' DELIMITED BY SIZE
40920 RUNTIME-PATH DELIMITED BY ' '
40920 'LCSWIN.LIB, L=' DELIMITED BY SIZE
40920 RUNTIME-PATH DELIMITED BY ' '
40920 'LCSIO.LIB, L="' DELIMITED BY SIZE
40920 RMCOBOL-PATH(1:PATH-INDEX) DELIMITED BY SIZE
40920 '\WOWRT.DLL"' DELIMITED BY SIZE
40920 ', L="' DELIMITED BY SIZE
40920 RMCOBOL-PATH(1:PATH-INDEX) DELIMITED BY SIZE
40920 '\LISQL.DLL"' DELIMITED BY SIZE
40920 INTO SYSTEM-COMMAND
40920 END-STRING.
CALL WINEXEC USING WIN-RETURN SYSTEM-COMMAND WIN-TRUE.

I am able to debug program A but I can't get into program B. Does anyone have a solution?

Thank you

Uwe Baemayr · Accepted Answer

Going to summarize a bit here. 
 You didn't give the actual command in SYSTEM-COMMAND (that is, the contents of the data item), so I tried to put it together myself. I gather it looks something like the bold string below. with $(..) being replaced by the contents of the various data items: 
 "$(RMCOBOL-PATH)\RUNCOBOL.EXE" $(ELMAIN) A="A$(PNF-EMPLOYEE-ID) $(PNF-FAMILY-MEMBER-ID)" L=$(RUNTIME-PATH)LCSWIN.LIB, L=$(RUNTIME-PATH)LCSIO.LIB, L=$(RMCOBOL-PATH)\WOWRT.DLL, L=$(RMCOBOL-PATH)\LISQL.DLL 
 In this case, $(RUNTIME_PATH) must end in a backslash while $(RMCOBOL_PATH) apparently doesn't. 
 It looks like SYSTEM-COMMAND is used like this: 
 CALL WINEXEC USING WIN-RETURN SYSTEM-COMMAND WIN-TRUE 
 If we assume the program that's issuing this command has a similar command line, unless LCSWIN.LIB or LCSIO.LIB implement WINEXEC with different semantics, it would be using the WINEXEC in WOWRT.DLL . 
 I checked and the WOW WINEXEC always creates a new process. I don't see any way that any version CodeWatch would ever step into a new process or automatically attach to such a process -- not in v10 or v12. There must be something else missing here. 
 CodeWatch does understand RM/COBOL command lines. Is it possible that you replaced " RUNCOBOL.EXE " with " RMCW.EXE " in the above command? I'm not certain CodeWatch processes all runtime commands but this might be worth a try. 
 In this case, you could try: 
 "$(RMCOBOL-PATH)\RMCW.EXE" $(ELMAIN) A="A$(PNF-EMPLOYEE-ID) $(PNF-FAMILY-MEMBER-ID)" L=$(RUNTIME-PATH)LCSWIN.LIB, L=$(RUNTIME-PATH)LCSIO.LIB, L=$(RMCOBOL-PATH)\WOWRT.DLL, L=$(RMCOBOL-PATH)\LISQL.DLL 
 Again, replacing the $(...) parts with the actual variables on the command line. 
 If there is something on this command line that CodeWatch doesn't understand, you could certainly create a CodeWatch workspace with the above settings and debug it that way. Since it's a separate process, it shouldn't inherit anything from the main program, although it would inherit environment variables. 
 This all assumes that the WOW WINEXEC is being used rather than another WINEXEC with different behavior.

Menu

RM/COBOL Discussions

Verified Answers

Debugging program called via WINEXEC

Top Replies

Resources