Overall Process For Implementing A Local Modification; The Localmod Step; Used Syntax Of Localmod; Examples - HP StorageWorks P9000 Software Installation Manual

12901
12902
12903
12904
12905
12906
12907
12908
In the above example, XEDIT lines 12889 through 12897 are the first line of code. The C characters
on the right side of some lines indicate the statement is continued. This provides formatting to make
the entries easier to read. To add the additional entries to the TMD33904 entry of the HCPMDPCD
macro, scroll through the file using XEDIT until you reach the location where the CCW entries for
CCW=83 and CCW=84 can be placed into the file and maintain the order. It is recommended
that the modification be notated as a local modification as appropriate for your local site processes
for code change documentation.

Overall Process for Implementing a Local Modification

To create and install a local modification is a four-step process composed of running LOCALMOD,
SERVICE, PUT2PROD, and re-IPL'ing the z/VM system.
Guide for Automated Installation and Service for your z/VM release contains more detailed
information. The most interactive step is the use of the LOCALMOD exec.
Creating and implementing a local modification is an activity that should be performed by one of
the system programmers that maintains the z/VM environment at your site. The proper
implementation of a local modification will involve following your local change control procedures.
Such procedures vary widely and cannot be discussed here in any detail. The system programming
staff at your site will be familiar with your defined procedures and be able to perform the local
modification process described here in a manner that conforms to the local change control and
testing procedures defined for your site.

The LOCALMOD Step

The LOCALMOD exec will need to be performed from the MAINT userid or a userid that has been
defined locally for performing maintenance activities. Before you begin, the software inventory
disk must be accessible. This disk is 51D by default and will be accessed as D. The complete syntax
and capability description of the LOCALMOD exec is beyond the scope of this appendix. The
following syntax describes the items that are needed for the local modifications needed to use
BCM with a z/OS guest running on z/VM.

Used Syntax of LOCALMOD

LOCALMOD component filenm filetyp (ASM HL
LOCALMOD is the name of the exec.
Text in bold type is entered as shown.
Component is the component that the local modification is to be applied to. It will be CP for the
modifications discussed here.
Filenm is the file name. It will be either HCPTDD (for the modification for dedicated disks) or HCPTMD
(for the modification for minidisks). To use BCM with both dedicated disks and full pack minidisks,
execute the LOCALMOD exec two times (one time for each modification) before performing the
SERVICE step.
Filetyp is the file type. It will always be ASSEMBLE for the modifications discussed here.
(ASM HL is an option to the LOCALMOD exec that specifies that the assembly operation is to be
performed using the High Level Assembler (HLASM). Note that the macros will not assemble
successfully using the default assembler provided with z/VM. HLASM must be used.

Examples

A typical LOCALMOD command for the dedicated disk modification would be:
STATMOD=NO,
SEEKREQ=NO,
RONLY=NO,
SPECIAL=YES,
SIMULAT=NO,
MULTI=NO,
LAST=NO
Requires special processing
"Glossary" (page 117)
Overall Process for Implementing a Local Modification
C
C
C
C
C
@VR4GHR3 C
@V11VXPX
SPACE 1
in the IBM manual
1 15