Difference between revisions of "Custom Compile Commands"

From MidrangeWiki
Jump to: navigation, search
(Cleaned up links, added link to the section under "WDSC tips", and additional notes.)
m (Added examples of compile command options to generate an event file.)
Line 8: Line 8:
  
 
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 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
 +
 +
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]
 
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]

Revision as of 20:06, 18 March 2010

To have the error list appear, your custom compile command must do two things:

  1. Produce the event file
  2. Include the following text items:
    1. *EVENTF
    2. SRCMBR(member-name)
  3. 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:

  1. Having *CURLIB set. If you don't the EVFEVENT file is created and populated in the library where you compile the object.
  2. 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.