Difference between revisions of "Custom Compile Commands"
From MidrangeWiki
m |
(Cleaned up links, added link to the section under "WDSC tips", and additional notes.) |
||
| Line 7: | Line 7: | ||
# 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> | # 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 | + | 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] |
| − | + | ||
| − | + | 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] | |
| − | 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 | + | 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]] | ||
Revision as of 01:16, 5 November 2009
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]
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.
