Difference between revisions of "Custom Compile Commands"
From MidrangeWiki
(New page with basic information on custom compile commands.) |
Starbuck5250 (talk | contribs) (+category RDi) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
## *EVENTF | ## *EVENTF | ||
## SRCMBR(<i>member-name</i>) | ## SRCMBR(<i>member-name</i>) | ||
| + | # Note: These items do not have to be active command parameters ... they can be referenced as a command comment (i.e., <code>/* *EVENTF SRCMBR(<i>member-name</i>) */</code> | ||
| + | |||
| + | See the IBM's technote (FAQ)[http://www.ibm.com/support/docview.wss?rs=3239&context=SSZND2&dc=DB520&dc=D600&dc=DB530&dc=D700&dc=DB500&dc=DB540&dc=DB510&dc=DB550&q1=compile&uid=swg21231854&loc=en_US&cs=utf-8&lang=en] | ||
| + | |||
| + | To produce the event file, the actual compile command must specify the proper options. (Note: Not every compile command has an option to generate an event file.) | ||
| + | |||
| + | Examples of compile command options to generate an event file: | ||
| + | |||
| + | CRTBNDRPG PGM(''mylibrary''/''myProgram'') SRCFILE(''mysource'') '''OPTION(*EVENTF)''' | ||
| − | |||
| − | |||
or | or | ||
| − | http:// | + | |
| + | CRTRPGPGM PGM(''mylibrary''/''myProgram'') SRCFILE(''mysource'') '''OPTION(*SRCDBG)''' | ||
| + | |||
| + | See also the section on Custom Compile Commands[http://wiki.midrange.com/index.php/WDSC_tips/Compile#Custom_Compile_Commands] under WDSC tips[http://wiki.midrange.com/index.php/WDSC_tips] | ||
| + | NOTE: The above section on ''Custom Compile Commands'' makes a few assertions which may no longer be required: | ||
| + | |||
| + | # Having *CURLIB set. If you don't the EVFEVENT file is created and populated in the library where you compile the object. | ||
| + | # Setting the *LDA with the library and member for the compiled source. Custom commands have been written which do not set the *LDA and still return the error list. | ||
| + | |||
[[Category:WDSC]] | [[Category:WDSC]] | ||
| + | [[Category:RDi]] | ||
Latest revision as of 23:15, 10 October 2016
To have the error list appear, your custom compile command must do two things:
- Produce the event file
- Include the following text items:
- *EVENTF
- SRCMBR(member-name)
- Note: These items do not have to be active command parameters ... they can be referenced as a command comment (i.e.,
/* *EVENTF SRCMBR(member-name) */
See the IBM's technote (FAQ)[1]
To produce the event file, the actual compile command must specify the proper options. (Note: Not every compile command has an option to generate an event file.)
Examples of compile command options to generate an event file:
CRTBNDRPG PGM(mylibrary/myProgram) SRCFILE(mysource) OPTION(*EVENTF)
or
CRTRPGPGM PGM(mylibrary/myProgram) SRCFILE(mysource) OPTION(*SRCDBG)
See also the section on Custom Compile Commands[2] under WDSC tips[3] NOTE: The above section on Custom Compile Commands makes a few assertions which may no longer be required:
- Having *CURLIB set. If you don't the EVFEVENT file is created and populated in the library where you compile the object.
- Setting the *LDA with the library and member for the compiled source. Custom commands have been written which do not set the *LDA and still return the error list.
