Previous Topic: 10.2 Program Modification and Extension

Next Topic: 10.2.2 Protocols and Functions

10.2.1 Modifying Distributed Code


If it is necessary to change distributed source code, you
must use the following procedures.


MODIFYING CODE IN MVS

When modifying code in MVS libraries, first save a copy of
the original code in sharedprefix.MICS.LOCALMOD.CNTL, then
apply any changes using IEBUPDTE.  Reassemble and relink the
affected modules as required.


MODIFYING CODE IN CMS

Although all maintenance for CA MICS VM code is delivered to
your MVS system and copied to your VM system, it may be
necessary to change some of the CMS files to apply temporary
changes or for tailoring purposes.

When modifying code in CMS, use the VMTXED command to edit
the original file and create a delta file of changes.
Regenerate the affected module, EXEC, or file using the
VMTGEN command.  Follow the steps below.

1.  To change the CMS files, enter the command:

    VMTXED fname ftype

    where fname is the file name and ftype is the filetype of
    the command or parameter list to be modified.  If ftype
    is not specified, VMTXED determines the appropriate file
    type.  For example, with VMTXED VMTFDEF, VMTXED searches
    for the file, and using XEDIT, presents file for editing.

2.  Once the changes are made, the command or file must be
    regenerated by entering the command:

    VMTGEN genlist ( GEN fname

    where fname is the name of the changed file and genlist
    is the name of the command generation list that contains
    the command sequence for generating the fname, e.g.,
    VMTGEN VMTGENU ( GEN VMTFDEF.


NOTE:  PLEASE be careful! All delivered files contain
sequence numbers.  Do not change these files, except with
VMTXED.  Because all delivered files can be replaced by
maintenance, any changes made directly are lost.  VMTXED
creates changes in a delta file so that local changes can be
tracked and maintained easily.