CONTROL CARD(S) .........1.........2.........3.........4.........5.........6.........7.........8 REPORT MEMORY=MVS FUNCTION=REPORT MEMORY=MVS

This page of the report shows the following:

The command exactly as entered.
An analysis of keywords encountered and expected. Any errors found are flagged with a note in the left margin.
Any messages related to syntax processing.

OPERATING SYSTEM z/OS V1.9 PROCESSOR 2097 SYSTEM CA11 CA DATACOM/DB SUBSYSTEM IS PRESENT

This page of the report shows the following:

OPERATING SYSTEM

This line starts with OPERATING SYSTEM, followed by the name that CA Datacom has identified as the operating system (z/OS in the example).

Following the operating system is the version and release that CA Datacom has identified.

Following the version and release is the word PROCESSOR followed by a number (2097 in the example) that CA Datacom has identified as the processor.

Following the number of the processor is the word SYSTEM, followed by the name identified as the system name where the DBUTLTY function executed (CA11 in the example).

SUBSYSTEM IS PRESENT

If the SUBSYSTEM IS PRESENT message appears on the new line, it shows that the CA Datacom/DB subsystem is in the operating system. When the subsystem is not in the operating system, this line shows CA DATACOM/DB SUBSYSTEM IS ABSENT. This SUBSYSTEM is used by and supports older CA Datacom releases prior to Version 14.0. It is not needed or used by 14.0 and should not be installed if there are no older CA Datacom releases present.

COMMON MEMORY USAGE (NOT SVC OR MUF SPECIFIC) ADDRESS SIZE TEXT 2F8AB000 4096 DB_SVC_AC R14.0+ SYSTEM ANCHOR 35FB4080 3AB51000 3540 DBPCCPR 14.0 20100727 15.55 CROSS MEMORY PC=PROD 3AB51000 3540 DBPCCPR 14.0 20100727 15.55 CROSS MEMORY PC=TEST 39448000 2738 DBPCSPR 14.0 20100808 10.36 PC XCF + RRS PC=PROD 00C77D04 36 SSCT 'DB ' AND SMALL ANCHOR 35FB4080 384 DBNSDBNB LARGE ANCHOR 35E65000 2082 DBESPPR 12 CROSS MEMORY 00C56000 632 DBSSVPR 12 SUBSYSTEM NUM I TYPE OPT. LOCK ADDRESS DBSVC DATE TM/SP SIZE 235 3/4 00B75D78 11.0 12/13/03 SP04 9932 239 3/4 394D0000 12 04/15/11 16.09 9024 MUF NAME STATUS REL JOB NAME JOB ID CXX NAME DC COMM31 ENBL-MDHMS COMMENTS DBDVM01 ENABLED 14.0 DBDVM0 JOB58297 DBDVM0 DB 4736 0628103948 DBDVM02 ENABLED 12 DBDVM02 JOB58894 DBDVM02 DB 4928 0628105229 SVC=239 DLV1M11D ENABLED 11.0 DLV1N11D AX11AD AD1839360 0627221559 SVC=231 COMMON24=192 JLM12RRM ENABLED 12 DBDVM0RM JOB58895 4416 0628105254 SVC=239 RRMNAME=JLM12RRM MSMDEVB ENABLED 11.0 MF2MUFB 00010MUF CAMSM AD 11904 0628124727 SVC=231 MSM COMMON24=192 MUFM DISABLED 14 DSNZMUFM STC59537 QAMUFM DB 23616 SVC=213 MUFM1 DISABLED 12 DSNZMUFM STC59622

This page of the report shows the following:

COMMON MEMORY USAGE (NOT SVC OR MUF SPECIFIC)

This section of the report provides common memory that is not an SVC and is not part of a specific MUF. This section of the report can be empty if no common memory has been allocated. Each item is printed with its address, size, and text that gives identifying information. In the sample, note the following:

The first line exists if Version 14.0 or a later release has built a system anchor.
The next lines exist for the executing PC supporting modules in memory. Possibly 4 for Version 14.0 with one for the DBPCCPR module to be used for production and one for test and one for the DBPCSPR module to be used for production and one for test.
The next lines exist is Version 12.0 or a earlier release has built a small and large anchor.
The next lines exist for Version 12.0 or earlier if additional modules are in common memory supporting the Subsystem and cross memory.

The next section reports any Datacom SVC’s that are installed.

NUM

NUM is the SVC number being reported.

I

I is the column that can contain the letter ‘I’ if the SVC appears to be invalidly defined.

TYPE

TYPE is the type of SVC such as 3 or 4.

OPT

OPT is the SVC option. Only blank or A are valid options for the CA Datacom/DB SVC.

blank: A blank indicates no option was specified.
A: An A indicates Assistable.
E: E indicates-use of the extended SVC router.
I: I indicates not preemptable.
P: P indicates the authorized program facility.
R: R indicates Access/Register mode.

LOCK

LOCK is the operating system lock required on entry to the SVC routine. The lock must be blank for the CA Datacom/DB SVC.

blank: blank indicates none required.
C: C indicates the CMS lock.
D: D - The dispatcher lock.
L: L indicates the local lock.
O: O indicates the optional lock.
S: S indicates the storage allocation lock.

ADDRESS

ADDRESS is the address of the location of the SVC.

DBSVC

DBSVC is the version number for CA Datacom/DB when this SVC was generated.

DATE

DATE is the date of the version for CA Datacom/DB when this SVC was generated.

TM/SP

TM/SP is a time of the version for the SVC.

Only SVC table entries from 200-255 are searched, and only those that appear as CA Datacom/DB are printed, except when the optional keyword SECURITY=YES is specified, in which case all SVC table entries in the range are printed (this assists in debugging, should that be necessary).

MUF Specific Common Memory Section:

MUFNAME

The MUF name, if known, is provided.

STATUS

The MUF status is provided as: ENABLED, DISABLED, EOJ SET.

Note: A shadow is not yet a MUF and has no identity.

REL

The Version release of the MUF last enabled

JOB NAME

The Job or started task name of the MUF last enabled

JOB ID

The Job ID or started task ID of the MUF last enabled

CXX NAME

The CXX name of the MUF last enabled

DC

The CA Datacom CXX type of DB for CA Datacom/DB, AD for [set the dad variable for your book], or blanks either if unknown or if this is an RRM address space supporting RRS.

COMM31

The size of common MUF specific memory allocated for this specific MUF.

ENBL-MDHMS

The date and time when the MUF was last enabled in the form of month-day-hour-minute-second

COMMENTS section can contain the following:

SVC=nnn: SVC=nnn occurs if the MUF is using a CA Datacom SVC.
SM: MSM occurs if this MUF is recognized as DATACOM MSM.
ENF: ENF occurs if this MUF is recognized as ENF, that is, if CA ENF is using a MUF within its own address space.
TR: TR occurs if this MUF is recognized as a Datacom TR
PC=TEST: PC=TEST occurs if this MUF is using the test versions of DBPCSPR and DBPCCPR
RRMNAME=name: RRMNAME=name occurs if this is not a MUF but an RRM supporting RRS