misi01 Advanced
 
  Joined: 02 Dec 2002 Posts: 629 Topics: 176 Location: Stockholm, Sweden
  | 
		
			
				 Posted: Fri May 20, 2022 4:40 am    Post subject: IDz. When are debug commands run and are usable | 
				     | 
			 
			
				
  | 
			 
			
				What I mean by this is the following. 
 
 
I have specified my commands data set as userid.IDZ.DEBUG.ZFEXXL2 with the following contents
 
 
 	  | Quote: | 	 		  
 
AT ENTRY ZFEXXL2;      
 
AT LABEL A-100;        
 
LIST W-BATCH;          
 
LIST TITLED W-BATCH;   
 
MONITOR LIST W-BATCH;  
 
 | 	  
 
 
and my preference data set as userid.IDZ.DEBUG.DEFAULT with the following contents:
 
 
 	  | Quote: | 	 		  
 
CLEAR LOG ;             
 
SET AUTOMONITOR ON LOG ;
 
 | 	  
 
 
Label A-100 is a dummy label I created for testing purposes, and is the first line after the procedure division line.
 
 
The log contains the following
 
 
 	  | Quote: | 	 		  
 
EQA2265I *** User preferences file commands follow ***
 
CLEAR LOG ;
 
 SET AUTOMONITOR ON LOG ;
 
EQA2431I Automonitor is on for this debug session.
 
EQA2454I This CU is not AUTOMONITOR capable for expressions.
 
The current location is ZFEDA0 at line 0x00000000
 
EQA2268I *** User preferences file commands end ***
 
EQA2266I *** Commands file commands follow ***
 
AT ENTRY ZFEXXL2;
 
 AT LABEL A-100;
 
EQA4849E The label variable is not in scope or does not exist in current compilation unit.       
 
 LIST W-BATCH;
 
 LIST TITLED W-BATCH;
 
 MONITOR LIST W-BATCH;
 
EQA2428E This command is either invalid or unsupported.
 
EQA2269I *** Commands file commands end ***
 
Program was stopped due to entry/function breakpoint on ZFEXXL2.                             
 
The current location is ZFEXXL2 at line          2
 
EQA4017I Load module DFSLI000 was loaded from LLA.  The load module information was processed from a data set found in file STEPLIB .                           
 
The current location is ZFEXXL2 at line       2949
 
 | 	  
 
 
When I debug, IDz stops at line 2 in ZFEXXL2 (not pointing to the procedure division).
 
 
I tried changing the label to a unique one (unique for ALL programs theoretically). I changed it from A-100 to A-ZFEXXL2 and then changed the debug file to 
 
 	  | Quote: | 	 		  
 
AT LABEL A-ZFEXXL2;    
 
LIST W-BATCH;          
 
LIST TITLED W-BATCH;   
 
MONITOR LIST W-BATCH;  
 
 | 	  
 
 (note that I removed the AT ENTRY line) but I still received the message
 
 
 	  | Quote: | 	 		  
 
AT LABEL A-ZFEXXL2;
 
EQA4849E The label variable is not in scope or does not exist in current compilation unit.      
 
 | 	  
 
 
So my question is this. If IDz is supposed (?) to emulate Debug Tool, what do I need to do (can I ?) in order to "prepare" a number of Debug Tool commands that have kicked in as soon as I enter and break in the relevant program? _________________ Michael | 
			 
		  |