Page of GC20-1801-10 As Updated April 1, 1981 by TNL GN25-0837 starter Systems
Then CMSXGEN loads all the text files needed to create the CMS shared
segment, starting at the address specified on the command line. If
there are any unresolved external references, the CMSXGEN command
terminates with the message: DMSCMS111E CMSXGEN FAILED DUE TO LOAD ERRORS To ensure storaqe protection for the named segment, CMSXGEN assigns a
storage key of X'D' (decimal 13) to the segment. CMSXGEN invokes the SETKEY command: SETKEY 13 segmentname
If any errors occur during the SETKEY command execution, the message: DMSCMS412S CMSXGEN FAILED DUE TO SETKEY ERROR is issued and
occurred during SAVESYS command. CMSXGEN execution is terminated. If no errors have CMSXGEN processing, the segment is saved via the CP If an error occurs at this point, the message: DMSCMS141S CMSXGEN FAILED DUE TO SAVESYS ERRORS is issued and CMSXGEN execution is terminated. Otherwise, the segment
is successfully saved, the load map is printed, and the completion
message: DMSCMS7151 CMSXGEN COMPLETE is issued. SAVING THE CMS SYSTEM Now, you should redefine your virtual storage to 960K and IPL CMS: define storage 960K ipl 190 -or- ipl 190 parm seg=segname Where segname is the shared segment created here, if not named CMSSEG. When the terminal unlocks, do not press 'ENTER', but immediately issue
the command:
savesys ems I Then press 'ENTER'. If CMS is successfully saved, the message
hh:mm:ss SYSTEM SAVED CMS VERSION n.n -mm/dd/yy hh:mm
is displayed. Your CMS system is now saved; you can issue IPL CMS instead of 1PL 190, when you wish to run CMS. If you named your CMS system something other than CMS, such as CMS1, the entry you made in the system name table would be for eMS1; you would have to save CMS1 (SAVESYS CMS1) and then you could 1PL CMS1. For more
information about how to save CMS, see the VMLJ70 or the "Saved Systems" section of this manual. At th is point, llse the Installation Verification Procedure (IVP) to
test the new system. Log off the userid MAINT and log on aqain as the
userid OPERATOR, using the password OPERATOR. The IVP is described
la ter in Part 3. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 259

11 fJ.L.1..1. I, I , Starter systems Step 25. Obtaining the MSS Communicator Program
If there is an MSS attached to your VM/370 system, and you plan to use
the DMKMSS program for communicating between the VM/370 control program
and the MSC, enabling VM/370 to dynamically mount and demount MSS volumes, you should obtain the file which will install the DMKMSS program in a VS system. The required file is distributed with the VM/370 control program object code, which you previously restored to
MAINT's 1q4. The first step is to ensure that MAINT has access to its
194. Issue the CMS command:
access 194 d/a
Next, punch the file; this will install DMKMSS in your VS system. If
your VS system is OS/VS1, issue the command:
punch mssvs 1 jcl
If your system is OS/VS2, issue the command:
punch mssvs2 jcl
The punched output you receive is a series of OS/VS jobs. This file
must be saved. When you execute the jobs in your OS/VS system, they
will install the DMKMSS program and create a VS operator procedure
called DMKMSS, later used to start the program in the communicator
virtual machine. OS/VS 1 JOBS There are four OS/VS1 jobs. They are: • LINKDMK -This job link edits the object code for DMKMSS into the SYS1.LINKLIB data set; the load module name is DMKMSS. The DMKMSS program must be located in SYS1.LINKLIB; this is one of the
requirements of APF (Authorized Program Facility). • DUMPT - This job prints two lists (named IEFSD161 and IEF161SD) in
the system program properties table. These lists are used in the
next job. • APFZAP - This job, as distributed with VM/370, replaces the module IEHATLAS and DMKMSS in the program properties table; this adds DMKMSS as an authorized program and removes IEHATLAS. If your installation
wishes to retain IEHATLAS as an authorized program, examine the lists
produced in job DUMPT above. Change the control statement provided
in APFZAP to add DMKMSS rather than replace IEHATLAS. • LINKPROC - This job adds the procedure DMKMSS to the SYS1.PROCLIB data set. You must place the communicator device address on the COMM control statement before running this job. After the job has
completed, the OS/VS1 system operator may start the DMKMSS program by
issuing the command' START DMKMSS. P*' where * is the number of the
partition in which DMKMSS is to run. 260 IBM VM/370 Planning and System Generation Guide