|
> Sorry to ask about something that's already been answered here > before, but I'm unable to find the message I thought I had saved. > Anyway, what are the steps to run the debugger on a program > submitted to batch? The easiest way is to inbed a "DLYJOB DLY(<# of seconds>)" at the beginning of the CL with enough time for you to bring the debugger up. david ---------------------------------------------------- Here is a suggestion I find _real_ handy: (but I don't know how it'd work in a batch process; I've never tried that) (This is not my creation, btw.) Here are 2 new commands you can easily add to your STRDM options to start debug for you. "I1" prompts you for the name of the starting place and "I2" calls that program. It works on CL and RPG. ---------------------------------------------------- In STRPDM, working with objects, ------------------------------------------------ - do F16 to get the list of commands. - do F6 to create a new command. - create the new command "I1" - the command is: "? STRISDB PGM(&N) UPDPROD(*YES) INVPGM(*CMD)" - return to theSTRPDM work with objects screen. - put I1 on the program you want to debug (CL & RPG both work). It will then prompt you for the command to call to start the debug session. That can be any command, including calling a menu. The procedure will work normally until it gets to the program you have marked to debug. ---------------------------------------------------- If you like that you can also make a command I2 - "STRISDB PGM(&N) UPDPROD(*YES)" and use that to directly call the object. ------------------------------------------------------- I can't take credit for these - someone unknown to me deserves that. ---------------------------------------------------- Booth Martin Contract Programming, Inc. --------------------------------------------------- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.