Preface
Terminology
This publication describes how to debugVM/SP and how to modify, extend, or
implement Control Program(CP) and Conversational Monitor System (CMS) functions. This information is intended for system programmers, system analysts,
and programming personnel.
This publication consists of three parts and three appendixes."Part 1. Control Program (CP)" contains an introductory and functional
description ofCP as well as guidance in implementing some CP features. "Part 2. Conversational Monitor System (CMS)" contains an introductory and
functional description ofCMS including how eMS handles interrupts and SVCs, structures its nucleus and its storage, and manages free storage. Information on
saving theCMS system and implementing the Batch Facility is also included. "Part 3. Debugging with VM/SP" discusses the CP and CMS debugging tools and
procedures to follow when debugging. This part is logically divided into three
sections. The first section,"Introduction to Debugging", tells you how to identify
a problem and lists guidelines to follow to find the cause. The second section
describes theCP debugging commands and utilities, debugging CP in a virtual
machine, the internal trace table, and restrictions. A detailed description ofCP dump reading is also included. The third section, "Debugging with CMS", describes the CMS debugging commands and utilities, load maps, and restrictions
and tells you what fields to examine when reading aCMS dump. "Appendix A: System/370 Information" describes the System/370 extended PSW and extended control register usage. "Appendix B: VM Monitor Tape Format and Contents" describes the format and
contents of data records for classes and codes ofMONITOR CALL. "Appendix C: CMS Macro Library" lists and describes the CMS macros applica
ble toVM/SP. Some of the following convenience terms are used throughout this publication:
Throughout this publication, the term"VM/SP" refers to the VM/SP program
package when you use it in conjunction withVM/370 Release 6. The terms "CP" and "CMS" refer to the VM/370 components enhanced by the func
tions included in theVM/SP package. Any reference to "RSCS," unless oth
erwise noted, is to theRSCS Networking Program Product (5748-XPl). Any
reference to"IPCS," unless otherwise noted, is to the IPCS Extended Program
Product (5748-SAl).
When you install and useVM/SP in conjunction with the VM/SP Release 6 System Control Program (SCP), it becomes a functional operating system that
provides extended features to the Control Program(CP) and Conversational
MonitorSystem (CMS) components of VM/370 Release 6. VM/SP adds no
additional functions to the Remote Spooling Communications Subsystem(RSCS) and the Interactive Problem Control System (IPCS) components of VM/370. However, you can appreciably expand the capabilities of these Preface vii
Terminology
This publication describes how to debug
implement Control Program
and programming personnel.
This publication consists of three parts and three appendixes.
description of
functional description of
saving the
procedures to follow when debugging. This part is logically divided into three
sections. The first section,
a problem and lists guidelines to follow to find the cause. The second section
describes the
machine, the internal trace table, and restrictions. A detailed description of
and tells you what fields to examine when reading a
contents of data records for classes and codes of
ble to
Throughout this publication, the term
package when you use it in conjunction with
tions included in the
erwise noted, is to the
reference to
Product (5748-SAl).
When you install and use
provides extended features to the Control Program
Monitor
additional functions to the Remote Spooling Communications Subsystem