Difference between revisions of "Test268 Section 7"
From MidrangeWiki
(→Use STRSRVJOB to debug a program running from another job) |
Kjburkhalter (talk | contribs) (→Use STRSRVJOB to debug a program running from another job) |
||
| Line 12: | Line 12: | ||
=== Use STRSRVJOB to debug a program running from another job === | === Use STRSRVJOB to debug a program running from another job === | ||
See [[Debug in Batch]] | See [[Debug in Batch]] | ||
| + | |||
| + | |||
| + | Long Hand | ||
| + | |||
| + | Submit your program into batch and make sure it is held. Do this by either holding the job queue that you are submitting the job to, or use the HOLD(*YES) option on the SBMJOB command. | ||
| + | |||
| + | * Use the WRKUSRJOB and display the job you with to debug with the display job option (5). | ||
| + | * Write down the user name, job name and number. | ||
| + | * Start a service job using STRSRVJOB entering the name, job name and number from the previous step. | ||
| + | * STRDBG PGM(YOURPGM) - Press F12 to exit the source display (Sorry, can’t enter breakpoints yet). | ||
| + | * Release your submitted job by releasing the job queue or the job itself. | ||
| + | * A display will appear asking you to press F10 function key. Press F10 and you will be brought to a command line. | ||
| + | * Enter DSPMODSRC and enter your breakpoints. | ||
| + | * Leave source display and command line by pressing F3 until you are back to the screen that asks you to press F10 to enter breakpoints. | ||
| + | * Press Enter to start your job. | ||
| + | * After that the job begins running and stops at the first breakpoint reached. | ||
| + | |||
| + | |||
| + | Short Hand | ||
| + | |||
| + | You can do what I did and create a command to combine these commands so that you only remember one command and not two. | ||
=== Code a trigger program using RPG === | === Code a trigger program using RPG === | ||
Revision as of 15:28, 2 January 2007
<< Previous Section | Home | Next Section >>
Contents
- 1 Section 7 - RPG problem solving/problem determination (9%)
- 1.1 Find and interpret messages on message queues and in a job log
- 1.2 Use STRSRVJOB to debug a program running from another job
- 1.3 Code a trigger program using RPG
- 1.4 Define and create unit test scenarios
- 1.5 Define and create integration test scenarios
- 1.6 Define and create system test scenarios
- 1.7 Diagnose and eliminate errors resulting from numerical operations (e.g. divide by zero, decimal data errors, arithmetic overflow)
- 1.8 Diagnose and eliminate level checks
Section 7 - RPG problem solving/problem determination (9%)
Find and interpret messages on message queues and in a job log
Use STRSRVJOB to debug a program running from another job
See Debug in Batch
Long Hand
Submit your program into batch and make sure it is held. Do this by either holding the job queue that you are submitting the job to, or use the HOLD(*YES) option on the SBMJOB command.
* Use the WRKUSRJOB and display the job you with to debug with the display job option (5). * Write down the user name, job name and number. * Start a service job using STRSRVJOB entering the name, job name and number from the previous step. * STRDBG PGM(YOURPGM) - Press F12 to exit the source display (Sorry, can’t enter breakpoints yet). * Release your submitted job by releasing the job queue or the job itself. * A display will appear asking you to press F10 function key. Press F10 and you will be brought to a command line. * Enter DSPMODSRC and enter your breakpoints. * Leave source display and command line by pressing F3 until you are back to the screen that asks you to press F10 to enter breakpoints. * Press Enter to start your job. * After that the job begins running and stops at the first breakpoint reached.
Short Hand
You can do what I did and create a command to combine these commands so that you only remember one command and not two.
