The CMRUN feature has been re-implemented to use newer internal technologies that are now available to optimize the way CMASAP jobs are submitted. With the exception of z/OS PDS Deployment, which requires two additional static JCL DD values, there are no differences in the way one uses CMRUN (for example. parameters) and the submission and response portions of a request run faster.

The output from the new implementation is slightly changed. The messages from the CMRUN executable now start in column 2 (previously in column 1), long informational and error messages are no longer truncated at 80, and there no longer are intermediate blanks lines in the output. The exit codes are unchanged. Any user scripts that parse CMRUN output should be adjusted for the change in starting column position and message length size.

For z/OS PDS, any existing custom JCLs that call the new CMRUN executable will need the addition of two DD names, as well as any high level qualifiers adjusted for the new software location. Any existing (pre 7706) z/OS PDS configurations that have had a 7706 (or higher) server upgrade will also need the same DD name additions to the configuration's CMRUN JCL example (if they use the CMRUN JCL or plan to use the CMRUN JCL). The JCL additions are:

//EDAERR DD DISP=SHR,DSN={hlq}.CFG
// DD DISP=SHR,DSN={hlq}.HOME.ERR
//CURFEX DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(1,1,10)),
// DCB=(RECFM=VB,LRECL=2044,BLKSIZE=27998,DSORG=PO)

Note: Use of the EDAAPI to submit CMASAP jobs (effectively a form of user written CMRUN) is now considered deprecated. Existing applications of this nature should be transitioned to the use of the standard CMRUN executable.