|
Rob, Your statement about the debugger: Granted the release of WDSC was a tad bit behind and I still didn't grasp that debugger (I still use the CODE debugger) Look for this article - "Thanks to Jef Sutherland's article in the May 2005 iSeries News" I am now debugging via WDSc using the service entry points and it's great. Here are a couple of things to be aware of: Once I debug my program, if I make changes and recompile my program, I need to reset the Service Entry Point by: 1)There is a drop down on the tool bar of Service Entry Point view (upper right corner of the view). Click on that drop down, and choose Clear all service entry point. Then set the service entry point on your newly compiled program again. This way, service entry point will be refreshed. AND #2) Proper authorities need to be set in order to use the Service Entry Point: . Your user profile must have sufficient authority to service a job running user the specified user id. . Your user profile should have *SERVICE special authority, and one of following: *ALLOBJ authority or *USE authority to the user profile of the specified user id. Give it a try, I would be surprised it you wouldn't change your ways. Good Luck! Diane M Mueller infosys5@xxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.