MODIFYBLD

The syntax for this command is as follows:

MODIFYBLD [{taskstring literal}]
MODIFYBLD [(usercode)]  [{taskstring literal}]

Use this command to modify the associated NGENnnSYS/BLD code file taskstring with the supplied value (must be "." terminated).

If Appl Bld is running under a usercode NOT defined in the Userdata file, then supply a valid usercode, (...).

To view the current BLD taskstring settings do not supply any argument.

The taskstring literal can be one or more of the following:

C=<Cobol85 compiler> ON <pack>
D=<Dmalgol compiler> ON <pack>
B=<Binder compiler> ON <pack>
T=<Compiler Target Level>
SETSTATS (Cobol85 runtime statistics capture is enabled – report and online)**
SETLIST (Cobol85 expanded listing including any INCLUDE files. Ideally, set this for a single Report/Ispec/Segment method deployment and then reset after the deployment, to avoid excessively large compiler listings. Output is written to printerbackup file *BD/<BLD mix>/.).**
SETMETHODS (Report Stub invoked method runtime statistics)**
SETRPC (Set to create the XML library interface definitions supporting an RPC capable Public Segment Methods library)

**SETSTATS requires a matching <system>/ENVIRONMENT _STATS codefile. Refer to the Agile Business Suite Runtime for ClearPath MCP Administration Guide Appendix G. AB Suite MCP Runtime Performance Measurement and Cobol85 Source Analysis for more information on these features.

Each of the literals must be separated by a comma with a final period (.) terminating the string.

For example:

MODIFYBLD C=(CMPUSER)SYSTEM/COBOL85 ON TEST, D=(CMPUSER)SYSTEM/DMALGOL ON TEST,
B=(CMPUSER)SYSTEM/BINDER ON TEST.
MODIFYBLD T=6, D=(CMPUSER)SYSTEM/DMALGOL ON TEST.

Note: “T=5” is interpreted as TARGET=LEVEL5. To determine whether to use “T=5”, check the COMPILERTARGET option on the MCP host to which you deploy your application before using the MODIFYBLD. If COMPILERTARGET is set to LEVEL5, use “T=5”.