Notes 1 If the update is being performed in
storage, the updated file in storage is
read line by line and a disk file is
created with the filename and filetype UPDATE CMSUT1. The filemode ... . .. , .
specltles tne dISK wnere me Tmal OUI put file resides. The disk file is then
closed. The UPDATE CMSUT1 file is then renamed $fname after the old $fname is erased.
Module DMSUPD 2 If RETCODE is not equal to zero, DMSUPD warning messages were issued during
the update. If update is being done in storage,
create the output disk file.
2 Issue messages as necessary.
Label Ref Notes
RETROO1 ment with the value of RETCODE in register 15. If no warning messages are issued and
the REP option is specified, the '$fname' file is renamed to 'fname', after the old file is erased. If the CTL option is specified and no
update files are found, the message DMSUPD181E NO UPDATE FILES WERE FOUND is displayed and control returns to the CMS command environment with a If warning messages are issued and the WR ETURN
return code of 40 in register 15. NOTERM option is specified, while
the REP option is not, the message DMSUPD1771 WARNING MESSAGES ISSUED (SEVERITY =nn)
is displayed (nn is the value in RETCODE). If warning messages are issued and the REP option is specified, whether or
not the NOTERM option is specified,
the message DMSUPD1771 WARNING MESSAGES ISSUED (SEVERITY = nn) 'REP' OPTION IGNORED is displayed (nn is the value of RETCODE). In either case, control
returns to the CMS command environ·
Diagra. 7-11. Exit processing If no warning messages are issued, and
no errors detected, control returns
to the CMS command environment
with a return code of 0 in register 15.
Updated File Module Label Ref I I I I I I NOUPDAT! Chapter 7. Procedures for Generating and Dpdating '1/370 141

Input Processing Output 1 Check that load list names and I I Load List -Ilb update identification level is
name
passed to VMFLOAD.
2 Check that the load list EXEC, and CNTR L file exist. If not found, return to CMS. .
3 Read update control file. CMS 4 Invoke the load list EXEC procedure
and build system load deck at 000. 5 Exit to CMS. . CMS Notes Module Label Ref Notes Module Label Ref
1 The load list name is moved into the VMFLOAD VMFLOAD
filename portion of a STATE com- mand line for an EXEC file and a CNTRL file. follow. The DMKLDOOE (nucleus loader) resident nucleus module must
be loaded first and followed by DMKPSA. The DMKCPE module must be the last resident nucleus The update identification level is
moved into the filename portion of
a RDBUF command line for an module loaded. The pageable nucleus modules are ordered so that they efficiently utilize page frames. The EXEC and CNTRL file. OM KSAV module must be loaded last. When the filename and filetype
2 Issue the STATE command via an VMFLOAD
are both specified, that specific file SVC 202 to make sure that the is searched for and punched, if found. load list EXEC and CNTRL files If the file is not found, it is skipped,
exist. If the load list EXEC file is NOLDL the message
not found, the message filename filetype NOT FOUND NO LOAD LIST is displayed, and processing continues
is displayed and control returns to the with the next item in the load list. CMS command environment with a
return code of 4 in register 15. When only the filename is specified, FNDM
the specified control file is used to If the load list CNTR L file is not NOCTR search for the highest level text file DINITD found, the message available. The first text file located NO CONTROL FILE is punched. If the search ends before SRTXT a text file is found, the "filename is displayed and control returns to the CMS command environment with a
return code of 2 in register 15. TEXT" file is punched if it exists. NOFILE If the file is not found, it is skipped,
the message
3 The first record of the control file is VMFLOAD DINITA filename filetype NOT FOUND
read and the class on the macro library is displayed, and processing continues
record is saved. with the next item in the load list. The rest of the control file is read. RDCTR This process continues until every
The control records are chained item in the load list is processed.
together in the proper hierarchy.
5 At this point, the text decks are loaded VMFLOAD ENOL If an error occurs while reading the BDCTR in the proper sequence in the specified control file, the message reader. All files not found vvere
ERROR IN CONTROL FILE identified by messages to the terminal. The message
is displayed and control returns to
the CMS command environment with SYSTEM LOAD DECK COMPLETE a return code of 3 in register 15. is displayed. The punch is set to stop spooling and is then closed. 4 The punch is set to spool continuously. VMFLOAD DINITB The load list EXEC procedure is
invoked by an SVC 202. The text Control returns to the CMS command RETERR
environment. files are punched in the order
specified in the load list. The resident nucleus modules are NOFILE loaded first and the pageable modules Diagram 7-12. The Nucleus Load Program 142 IBM VM/370 Service Routines Prograa Logic