Method of Operation This section describes the VM/370 interface tetween CMS (the Conversational Monitor Syste.) and the OS/VS EREP progra •• Diagrams 11-1 and 11-2 describe the
functions of the interface .odules and
serve as a guide to the progra. listings. The labels shown indicate the closest, non.acro expansion label to the function OS/VS EREP I Diagram 11-1 DMSIFC being docu.ented. These diagra.s are not
terribly detailed, therefore, seme functions are not shown. Use the Directory
and Progra. Organization section to find
the labels in the progra. listings for any routines that are not shown in the Method of Operation section. Pigure 11-1 shows the
relationship of these diagra.s. I Diagram 11-2 DMSREA Figure 11-1. Key to EREP/Error Recording Interface Method of Operation Diagra.s
212 IBM VM/370 Service Routines program Logic

Input Output
REG 1 1---. Parameter
List of
optional
fileid from
the com­ mand line
Initialize. ======>1 2 Define files.
3 Determine source of control card
parameters.
REG 1
Control
Parameters 1--'---1 -> '11r==>1 -2-J I 4 Construct parameter list and
control card file. hr I 5 Handle special requests. I 6 Uok to DSNS EREP (lFeEREP1 Jrib I I B Data from ur error recording 1 __ CY_linders ---II 7 Trap EXCPs to SYS1.LOGREC I issued by OS/VS EREP. Simulate n EXCP operation calling on n DMSREA to supply data from VM/370 error recording cylinders. i Notes Module Label Ref Notes
1 The initialization procedures include: DMSIFC DMSIFC Diagram CLEARF parameter (determines • Standard linkage and addressability
11-1
functions. • Loading and resolving VCONs in OS/VS EREP decks. • Loading DMSREA. • Turning off flag in CMS nucleus to
cause OS simulation. • Setting COMPSWT in CMS nucleus
to load LINK and LOAD macros
validity by examining processor
identity. If not 3031,3032, or 3033 processor reject command
but if valid, erase error records
from the error recording cylinders
then initialize SRF frames to the
beginning of the error recording
cylinders.) • CLEAR parameter.
to be entered in TEXT files. • TERMINAL parameter (stops • Establishing handling of SVC 76, SVC 18, and SVC O. reading from control file on disk
and goes to terminal to read addition-
al control parameters) . ., liivoke FILEDEF to define: 1< • Printer file (EREPPT). I INDRWD'S. • SYSIN file (SYSIN). RDYACC • Dummy file for SYS1.LOGREC RDYHIST (SERLOG). OPER12 • Error file (TOURIST). • Work file (DIRECTWK). • Accumulation tape fi Ie (ACCD EV). • SHARE parameter. • CTLCRD parameter. • ACC parameter. • HIST parameter. • MERGE parameter. • MES and THRESHOLD parameters. • RDESUM parameter. • ZERO parameter. • History input tape (ACCIN). 6 Load the address of the word that
3 Determine where control parameters HAVETYPE are to be taken from (Control file NOEXTRA points to the OS PARM list built for OS/VS EREP and LINK to IFCEREP1. or terminal). BADATTR GOODATTR 7 EXCP SVCs from EREP are inter-
cepted and simulated so they appear
4 Set up to read parameters. Obtain Diagram
storage for OS PARM list to be passed 11-1
to EREP. Read control parameters, PARMWORI< generating the OS PARM list and a RDERR1 SYSIN file as output. Call subroutine PLiSTBLD to access a SYS1. LOG R EC data set. Simulation causes calls to DMSREA for VM/370 error records. BLDL SVCs from EREP are also trapped and
simulated by DMSIFC. to read control parameters. Handle
errors.
5 If CLEAR is specified with other WANTCLR
parameters, type an error message. CLEARRTN If CLEAR is specified properly, call
subroutine to erase error records from
the VM/370 error recording cylinders.
Subroutines handle each parameter
information:
Diagraa 11-1. DftSIFC DMSIFC826E DMSIFC023E DMSIFC070E DMSIFC002E DMSIFC007E DMSIFC831E DMSIFC104S OSPARM list for OS/VS EREP DMSIFC825E DMSiFC82S; DMSIFC829W DMSIFC832S Module Label Ref
HCLEARF
HCLEAR
HTERM HSHARE HHIST HMERGE HMES HRDESUM HZERO ::lMSIFCO DMSIFC18 Chapter 11a DftSIFC and DftSB!I--ERlP/Error Recording Interface 213