Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837
Updating CMS Update Procedures for CMS/VSAM and Access
Method Services You are responsible for ordering and applying all updates to DOS/VS that
affect the VSAM and access method services routines and the DOS logical
transients ($$BOMSG1, $$BOMSG2, $$BOMSG7, and $$BENDQ) that CMS distributes. You can order these updates in card form or on tape.
If you order the updates on cards, you must remove all of the DOS/VS job control statements from each PTF (program temporary fix) deck and
place a CP ID at the beginning of the deck. The CP ID card must
contain the userid of the CMS virtual machine that is being used to
update and access method services.
For example, if you vant to apply an update to a module using the
MAINT virtual machine, your ID card is:
ID MAI}1T If you installed VSAM and access method services under eMS as an OS user, VSAMGEN created eMS text files for all the required DOS/VS relocatable library modules. Now you need not have a DOS/VS relocatable
library for updating. CMS creates text files from the updates and
replaces the old text files on your A-disk with the new text files.
Text files must have a filetype of TEXTe For example, after you have
updated an object module using VMFASM, the most recent object file has a
filetype such as TXTLOCAL. To use that text file here, you must rename
it to a filetype of TEXT. If there is currently a text file on the systeID disk, you may want to rename it too, so that your updated text
file (which may reside on another disk) is the one that is loaded. VSAMGEN UPDATE CONSIDERATIONS Applying DOS/VS PTFs to either the CMSVSAM or the CMSAMS discontiguous
saved segments may result in the generated segment exceeding the space
defined for it in the system name table (see the NAMESYS macro of the DMKSNT module). You may want to anticipate this problem by defining in
the system name table an additional shared and nonshared segment for
each of the discontiquous saved seqments (CMSVSAM and CMSAMS). This is
one way of providinq for additional Alternatively, upon completion of the VSAMGEN update procedure, you
can check whether the updated segments have exceeded their definitions
and correct that situation as follows:
1. Determine the new size of the changed VSAM and/or access method
services shared and nonshared segments by subtracting the phase LOCORE address from the BICORE address indicated on the linkage
editor map. The phase names are:
2. • Dr-:[ SVVS - VSAM shared • Dl'lSVV}1 - VSAM nonshared • DMSVAS - access method services shared • DMSVAN - access method services non shared • DMSV33 - VSAM shared (DOS/VS Release 33 or 34)
Compare the new sizes of these segments with the sizes of
correspondinq shared or nonshared segments as defined in DMKSNT NAMESYS macro.
the
your Part 5. Updating VM/370 357

Ul. lOV 1- IV AB I, DY ,,!'NL GNL!)-Utsj I Updating CKS 3. If the new size exceeds your defined size, recode the NAMESYS macros to include an additional segment. Refer to the phase names
listed in step 1 to determine whether the segment is shared or
nonshared. To add one segment: • Increase the SYSPGCT operand by 16 • Increase the SYSPGNM operand by 16 • Increase the SYSHRSG operand by 1, if the segment is shared • Increase the SYSSIZE operand by 64K • Change the SYSSTRT operand of this or other segments, if the
increase in this segment causes any segments to overlap
4. Reassemble the DMKSNT module, build a new CP nucleus, and then
reexecute theVSAMGEN procedure.
If a PTF .contains a new VSAM or access method services module, it is nat included in or during VSAMGEN you have level of installation files.
If you want to use a new release level of DOS/VS, you must regenerate
the CMSVSAM and CMSAMS segments using the starter system supplied by DOS/VS. VM/370 provides new installation EXECs and DOSLNK files,
which vou must use to install the new release properly. The
installation procedure is described in Part 3. It is not necessary to regenerate existing Cl!SVSAM and CMSAMS segments using the Release 34 starter system. If you do so, however,
you must be sure that the space allocation for the CMSVSAM segment in
the system name table (D!'!KSNT) file is increased to five shared segments
and one nonshared segment, and the space allocation for the CMSAMS segment is increased to 6 shared segments and 2 nonshared segments.
Note that the segment addresses above these segments must be increased
accordingly. USING VSAMGEN TO UPDATE Cl!S VSAM AND ACCESS METHOD SERVICES Before you invoke VSAMGEN, do the following: • Access a read/write disk as your A-disk. This disk must be the
same disk that you used as your A-disk when you installed VSAM and
access method services. • If you are a DOS user, link to and access the DOS/VS system disk. • If you are applying PTFs from tape, a tape drive must be attached at
virtual address 181 and the PTF tape must be mounted and positioned
at the first tape file you want processed. VSAMGEN assumes that the PTF tape is unlabeled and contains 3440-byte blocks of records. Use the VSAMGEN EXEC procedure to update VSAM and Access Method Services support in CMS. Invoke VSAMGEN as follows:
vsamqen
358 IBM VM/370 Planning and System Generation Guide