Generate the DMCL load module by issuing a GENERATE statement. Optionally, identify the operating system under which the DMCL will be used. For example, you can define a DMCL on a z/OS operating system that will be used under z/VM:
generate dmcl idmsdmcl for vm;
Punch the DMCL load module using the PUNCH DMCL LOAD MODULE utility statement:
punch dmcl load module idmsdmcl;
Link-edit the resulting object module to a load library using the linkage-editor for your operating system. The name under which you link the DMCL is the name by which the DMCL is known at runtime. Therefore, you can define different DMCLs and link them all with the same name provided they reside in different load libraries. This can be an advantage for local mode operations since the default DMCL used at runtime is IDMSDMCL, unless a SYSIDMS parameter is used to override the default.
Identify the DMCL to the runtime system:
|
Copyright © 2014 CA.
All rights reserved.
|
|