System Control File
Preparing the CP System Control File (DMKSYS) The CP system control file consists of macros that describe the CP system residence device, the system storage size, the CP-owned direct
access devices, the system operator's user identification, the system
timer value, the system pointer variables, automatic performance
monitoring parameters, and security journaling parameters. The
installation is responsible for ensuring the presence and accuracy of
the macros described below.
The DMKSYS ASSEMBLE file provided with the starter
assemble properly unless you have reserved adequate
nucleus.
system does not
space for the CP The file should be placed in the card reader in the order shown: DMKSYS CSECT SYSOWN macro SYSRES macro SYSOPR macro SYSCOR macro SYSTIME macro SYSMON macro SYSJRL macro SYSLOCS macro
END
1. Samples of the DMKSYS and DMKSNT files are provided with the
starter system. If you use these, you can save the eMS system at
the end of the system generation procedure. VM/310 prompts you to
tell it if you want the sample DMKSYS file punched. You may modify
this file if you wish. For example, you could modify the starter
system DMKSYS file to add other CP-owned volumes.
2. SYSLOCS must always be the last macro coded.
The DMKSYS module supplied with the 2314 starter system is: DMKSYS CSECT SYSOWN (VMRELn
1 ,TEMP)
SYSRES SYSVOL=VMRELn,SYSRES=131,SYSTYPE=2314,SYSNUC=12, SYSWRM=16,SYSERR=17,SYSCKP=(101,2) SYSOPR SYSOPER=OPERATOR,SYSDUMP=OPERATNS SYSCOR RMSIZE=512K SYSTIME ZONE=4,LOC=WEST,ID=EDT SYSMON AUTO=NO SYSJRL SYSLOCS END
x lVMRELn may be VMREL1, VMREL2, VMREL3, and so forth depending on the
release leve 1. Part 2. Defining Your VM/370 System 163
system Control File
The DMKSYS module supplied with the 3330 starter system is: DMKSYS CSECT SYSOWN (VMRELn
1 ,TEMP)
SYSRES SYSVOL=VMRELn,SYSRES=131,SYSTYPE=3330,SYSNUC=7, SYSWRM=10,SYSERR=1',SYSCKP=202 SYSOPR SYSOPER=OPERATOR,SYSDUMP=OPERATNS SYSCOR RMSIZE=512K SYSTIME ZONE=4,LOC=WEST,ID=EDT SYSMON AUTO=NO SYSJRL SYSLOCS END
The DMKSYS module supplied with the 3340 starter system is: DMKSYS CSECT SYSOWN (VMRELn
1 ,TEMP)
x SYSRIS SYSVOL=VMRELn,SYSRES=131,SYSTYPE=3340,SYSNUC=15, X (17U.3) SYSOPR SYSOPER=OPERATOR,SYSDUMP=OPERATNS SYSCOR RMSIZE=512K SYSTIME ZONE=4,LOC=WEST,ID=EDT SYSMON AUTO=NO SYSJRL SYSLOCS END
The DMKSYS module that is used with the 3350 starter system is: DMKSYS CSECT SYSOWN (VMRELn
1
,TEMP)
SYSRES SYSVOL=VMRELn,SYSRES=131,SYSTYPE=3350,SYSNUC=4, SYSWRM=6, SYSERR=7.,SYSCKP=,277 SYSOPR SYSOPER=OPERATOR,SYSDUMP=OPERATNS SYSCOR RMSIZE=512K SYSTIME ZONE=4,LOC=WEST,ID=EDT SYSMON AUTO=NO SYSJRL SYSLOCS END
Performance Considerations for Coding the DMKSYS File Macros X The following recommendations may help reduce arm and channel contention
and may improve the performance of a VM/370 system. Provide separate CP volumes for paging and spooling and have the
volumes mounted on separate channels. If you have a heavy I/O production virtual machine (for example, one
that is executing OS/VS1 or DOS/VS), try to keep all its major 110 devices on a separate channel from a channel handling the CMS system
residence volume or other user's disks. Try to keep read-only mini disks
residence disk and source disks)
(for example, the CMS system
that are frequently accessed on IVMRELn may be VMREL5, VMREL6, and so forth, depending on the release
level.
164 IBM VM/370 Planning and System Generation Guide
Previous Page Next Page