Glossary

Descriptions of key terms
cmfzs
Contents
ACL
ACL
is the abbreviation for automatic cartridge loader, a feature available on IBM 3480-type tape devices.
ACL processing
ACL processing
is special processing that z/OS performs for IBM 3480-type devices in which the automatic cartridge loader (ACL) feature is installed and active. When the ACL feature of a device is installed and active, z/OS tries to use that device for only nonspecific, non-temporary volume requests.
action message
An
action message
is a message that is assigned a descriptor code of 1 (system failure messages), 2 (immediate action messages), 3 (eventual action messages), or 11 (critical eventual action messages). Action messages with descriptor codes of 1, 2, or 11 notify you of important events and are displayed on consoles as highlighted, non-deletable messages. Also see
descriptor code
.
active ACL status
An
active ACL status
is a type of device status that you can assign through the CA MIA VARY command. You can assign active ACL status only to IBM 3480-type devices on which the ACL feature is installed. When you change the ACL status to active, z/OS performs ACL processing on that device during allocation.
active status
See active ACL status.
address routine
An
address routine
is an optional routine in the CA MIA application program interface. This routine retrieves the Unit Control Block (UCB) names of all devices on the local system. A sample routine named API1SM02 is provided in the CAI.CBTDSAMP data set.
alias name
See system alias.
allocation recovery
Allocation recovery
is the part of the z/OS device allocation process that a job enters when it cannot allocate a suitable online device. During allocation recovery, z/OS determines how to handle that job (cancel it, make it wait for a device to become available, or vary a suitable offline device online). Based on this information, z/OS issues messages IEF238D (and sometimes other additional messages) to tell you what your options are. You can use the SETOPTION command, the CA MIA VARY command, and the TPCRECXT exit routine to influence allocation recovery when TPCF is running.
alternate path support
Alternate path support
is a z/VM feature that lets you define alternate channels from a real processor to a DASD or to a tape device to improve performance.
ASCB CHAP
ASCB CHAP
is a z/OS function that GDIF uses to change the dispatching priority of a user address space during critical ENQ processing.
assignable tape devices
Assignable tape devices
refers to the following types of devices: 3480, 3490, 3590, and any other type of compatible tape device.
attribute verification
An
attribute verification
is an EDIF feature that you can use to prevent programs from making inappropriate changes to the attributes of a data set. During attribute verification, EDIF determines whether a non-exempted program will change the attributes of a data set. If so, then EDIF records the violation. EDIF also abends the program to prevent the update if the ABEND option is in effect. You can enable this feature by specifying the ATTRIBUTES option on an EDIF processing statement.
attribute violation
An
attribute violation
is an update in which the attributes of the data sets will be changed by the program if the update takes place. The EDIF attribute verification feature lets you detect attribute violations and prevent attribute changes from taking place.
authority level
An
authority level
is an assigned code that determines which cross-system commands a target console can execute. You can assign an authority level to a target console through the AUTHORITY parameter on the LINK command. However, the LINK command does not change the z/OS authority level for that console. z/OS authority levels determine which local commands a console can execute.
authorization statement
See the glossary definition for
LMP codes
.
AUTOFREE
AUTORFREE
is an ECMF feature that automatically frees certain data sets that were dynamically allocated by TSO users and are currently marked not in use.
broadcast
Broadcast
is the process in which GCMF sends cross-system messages to a group of consoles based on criteria defined in a collection set.
CALServ
CA
-
L
-
Serv
is a component of CA Common Services for z/OS that allows CA MIC to route commands and messages across systems, as an alternative to using CTC or DASD control files. CA-L-Serv uses VTAM to communicate information among systems. The Intersystem Communication Facility (ICMF) must be active before you can use CA-L-Serv.
checkpoint files
Checkpoint files
are non-shared DASD files used to track system status information when using CTCONLY or XCF communication methods. They are also required for the REQUEUE feature of the ECMF facility within CA-MII to track job status information when CA-MIM is shutdown and then restarted.
collection set
A
collection set
is a message routing definition that allows a local console, product, TSO user, or system log to receive messages from one or more external systems. Collection sets are created through the COLLECT command.
command
A
command
is a line of text that establishes elements of the
CA MIM for z/OS
operating environment that you can change while it is running. You can issue commands from the MIMCMNDS or MIMSYNCH member of the parameter data set, from a console, or from a TSO session.
command alias
A
command alias
is a site-defined alias that you can substitute for a
CA MIM for z/OS
command, using the DEFALIAS command. For example, if you define the alias DS for the DISPLAY SYSTEMS command, you can specify DS when you want to see status information about the systems in your complex, instead of specifying DISPLAY SYSTEMS.
command prefix character
A
command prefix character
is a character that you can use to prefix
CA MIM for z/OS
commands. Assign this character using the CMDPREFIX parameter on the SETOPTION command.
command routing path
A
command routing path
is a path between a local console, product, or TSO user and one or more external systems. This routing path enables that console, product, or TSO user to issue commands to the external system and to receive the cross-system responses to those commands. Command routing paths are created through the LINK command. Command routing paths are also known as linkages.
command source
Command source
is the product, TSO users, or consoles authorized to issue cross-system commands through a linkage.
communication method
You must select a
communication method
to allow
CA MIM for z/OS
to share important information between systems. The methods available for use are DASDONLY, CTCONLY, CTCDASD, XCF, ICMF, and NONE.
conflict
A
conflict
is a situation in which two or more tasks need access to the same resource at the same time and cannot share access to that resource.
console pool
A
console pool
is a group of consoles from which GCMF can allocate a console to execute a cross-system command. GCMF uses the pool only for dedicated and shared linkages. Consoles in this pool are known as console pool members.
console pool member
A
console pool member
is a console in the GCMF console pool. Inactive MCS consoles and subsystem consoles may be members of the console pool.
control file
A
control file
is a data set that
CA MIM for z/OS
uses to communicate information among systems, to store checkpoint data, or both. When CTCDASD or CTCONLY are active,
CA MIM for z/OS
uses a
virtual control file
to communicate information. DASD control files are used for DASDONLY communication and as a backup control file for CTCDASD. You also can define backup (or alternate) DASD control files, which are used if the current control file becomes unusable.
coupling facility
The
coupling facility
is a combination of hardware and software technologies that provide z/OS components and subsystems with the ability to share and transport data among systems in a sysplex.
CP
CP
is an abbreviation for Control Program, the portion of the z/VM operating system that manages real resources (such as real memory) and I/O operations to tape devices, printers, and so on.
CPU
CPU
is an abbreviation for central processing unit, the portion of a computer that controls overall activity and fetches, decodes, and executes instructions.
CPU image
See
image
.
CTC device
A
CTC device
is a Channel-to-Channel Adapter or IBM 3088-type device that is physically connecting two systems.
CTC master system
See master system.
CTC path
A
CTC path
is a logical path connecting two systems. You need to define CTC paths when you are using the CTCDASD or CTCONLY communication methods so you can transmit cross-system information across CTCAs or IBM 3088-type devices. CTC paths do not connect systems physically; you need to use CTCAs or IBM 3088-type devices to connect systems physically.
CTCA
CTCA
is the abbreviation for Channel-to-Channel Adapter, a device that you can use to connect two systems physically.
DASD
DASD
is an abbreviation for direct access storage device.
data set control block
A
data set control block
is a data set label that describes the DASD space and attributes for a data set on a DASD device.
DCB
DCB
is an abbreviation for data control block, an interface between an executing program and a data set.
deadly embrace
A
deadly embrace
is an unresolvable set of conflicts in which tasks on different systems lock each other out of the devices or resources that the tasks need to complete. For example, if task 1 controls device 1 and needs device 2, and task 2 controls device 2 and needs device 1, neither task can complete. You must cancel these tasks to end the conflict.
dedicated device
A
dedicated device
is a device that has been given dedicated status through the CA MIA VARY command.
dedicated linkage
A
dedicated linkage
is a linkage in which a single console pool member is used as the target console. Any other linkages cannot use that console pool member. Specifying POOL=DEDICATE on the LINK command creates dedicated linkages.
dedicated resource
A
dedicated resource
is a data set or device that is reserved for a particular system, program, function, or user.
dedicated status
Dedicated status
is a type of device status you can assign through the CA MIA VARY command. Dedicated status identifies a device that can be allocated only on one system, unless no other suitable device is available. A locally dedicated device is a device that is dedicated to the local system (that is, the system you are currently on). An externally dedicated device is one that is dedicated to a different system.
descriptor code
A
descriptor code
is code used by MCS to route a class of messages to consoles. Descriptor codes identify types of messages; for example, system failure messages (descriptor code 1), immediate action messages (descriptor code 2), eventual action messages (descriptor code 3), or critical eventual action messages (descriptor code 11). These messages provide you with information about system status, situations that require the attention of an operator, and so on. Although many messages are assigned descriptor codes, some messages do not have them. You can use the z/OS CONTROL V,LEVEL command to select messages for each MCS console, based on the descriptor code assigned to those messages.
destination
The
destination
is the local consoles, TSO users, product, or system log that is receiving cross-system commands gathered by a collection set.
device control list
A
device control list
is a series of entries that provide CA MIA with information about devices that it should be managing. See MIMUNITS member.
device control member
The
device control member
is the optional member that provides CA MIA with the local and global names of the devices that it should be managing. This member is identified through the DEVLIST parameter on the MIMINIT statement. By default, CA MIA uses the member named MIMUNITS.
device group
A
device group
is a set of devices created by z/OS during the system generation process. z/OS systems use device groups in creating the eligible device list, from which it selects a suitable device for allocation. Each device group contains one device.
device preference value
A
device preference value
is a type of device status you can assign through the CA MIA VARY command. TPCF uses these values to preference a device from a group of otherwise equally acceptable devices. The higher the value you assign, the more preferenced the device.
DISP=SHR verification
DISP=SHR verification
is an EDIF feature that you can use to prevent programs from updating a data set when DISP=SHR is specified in the JCL of the job. The value DISP=SHR does not prevent other programs from updating the data set at the same time. When you enable this feature, EDIF examines the JCL for the programs you designate when one of those programs tries to update the data set. If DISP=SHR is specified, then EDIF records the violation. EDIF also abends the program to prevent the update if the ABEND option is in effect. You can enable this feature by specifying the CHECKEXCLUSIVE parameter on an EDIF processing statement.
display command
A
display command
is a command that you can use to obtain information about resources, devices, messages, systems, and so on. You can issue these commands from the
CA MIM for z/OS
parameter data set, from a console, or from a TSO session.
display panel
A
display panel
is an optional panel in the CA MIA application program interface. This panel shows you status information for the managed devices you name on a retrieval panel. The name of the display panel is API1PNL2.
display routine
A
display routine
is an optional routine in the CA MIA application program interface. This routine enables you to display information about tape devices on an ISPF screen. The name of this routine is API1SM01.
DSCB
DSCB
is the abbreviation for data set control block.
dual allocation
A
dual allocation
is a situation in which two or more jobs concurrently allocate the same device.
ECMF
ECMF
is an acronym for the ENQ Conflict Management Facility, which is available with the CA MII component. ECMF issues messages when a resource conflict occurs. ECMF also resolves certain types of conflicts automatically.
EDIF
EDIF
is an acronym for the Enhanced Data Set Integrity Facility, which is available with the CA MII component. EDIF detects and prevents common user errors that can compromise data set integrity.
EDIF processing list
An
EDIF processing list
is a series of EDIF processing statements that tell EDIF what types of data set damage to detect or prevent. A sample processing list is provided in member EDIPARMS in the CAI.CBTDPARM data set. The member that contains this list is called the EDIPARMS member throughout the
CA MIM for z/OS
documentation.
EDIF processing statement
An
EDIF processing statement
is a statement that tells EDIF what types of data set damage to detect or prevent for a group of data sets or for a single data set. The DEFAULT, DSORG, PREFIX, SUFFIX, PATTERN, and DATASET statements are all EDIF processing statements. The UTILITY statement is a special type of EDIF processing statement identifying programs that should be processed the same way.
EDIPARMS member
The
EDIPARMS member
is a member of the parameter data set that contains EDIF processing statements, which tell EDIF what types of data set damage to detect and prevent. Collectively, the contents of this member are called the EDIF processing list. A sample member called EDIPARMS is provided in the CAI.CBTDPARM data set.
EDL
EDL
is the abbreviation for eligible device list. Also see eligible device list.
EDT
EDT
is the abbreviation for eligible device table, a table of device addresses used during device allocation. Also see eligible device table.
eligible device list (EDL)
An
eligible device list (EDL)
is a list of devices that z/OS builds for a device allocation request. The eligible device list contains the unit control block address of every device with the correct physical characteristics for that request. The eligible device list consists of one or more device groups that contain these device addresses.
eligible device table (EDT)
An
eligible device table (EDT
) is a list of devices from which z/OS chooses during device allocation. The eligible device table contains the unit control block address of each device known to the local system. When a job requests a device, z/OS extracts the addresses of the devices with the correct physical characteristics for that request. This list of device addresses is known as the eligible device list.
elimination logic
Elimination logic
is the logic in the TPCEDLXT exit routine and job reserve processing that TPCF uses to eliminate unwanted devices before z/OS allocation processing begins. TPCF uses this logic to remove devices from the z/OS eligible device list during allocation; TPCF also uses this logic to eliminate devices from the z/OS offline device list during allocation recovery.
ENQ facility
The
ENQ facility
is a z/OS facility that serializes access to resources in a system. The ENQ facility establishes a queue of tasks waiting to use a resource, and the system control program manages this queue. A task (or z/OS) issues an ENQ request to use this facility. Also see ENQ request.
ENQ request
An
ENQ request
is a request that uses the z/OS ENQ facility to serialize access to resources that will be used by multiple tasks on the same system.
A task can request shared or exclusive access to a resource. Shared access usually means that the task does not update the resource; therefore, other tasks can share access to that resource at the same time. Exclusive access usually means that the task will update the resource so that other tasks cannot share access to that resource at the same time without risking an integrity exposure.
A three-part naming convention is used on an ENQ request: the major name (or QNAME) of the class of resources, the minor name (or RNAME) of the specific resource that is needed, and the scope, which indicates whether the task will serialize access in its address space, in the system, or among systems. Also see QNAME and RNAME.
esoteric group
An
esoteric group
is a site-defined group of devices. Esoteric groups are created through the UNITNAME macro. Esoteric groups have a critical effect on the device groups z/OS creates for an allocation request.
exclusion parameters
Exclusion parameters
are parameters on the COLLECT command that tell GCMF to exclude certain messages that otherwise would be collected by that collection set. You can use exclusion parameters to collect only a subset of any message category. For example, you can collect all messages issued by a job, except a message you name on an exclusion parameter. A collection set never collects messages you specify on an exclusion parameter, even if another parameter in that collection set selects those messages. Also see inclusion parameters.
exclusive linkage
An
exclusive link
is a linkage in which you specifically assign a console as the target console. Specifying the TGTCONS parameter on a LINK command creates exclusive linkages. Also see target console.
exempt list
An
exempt list
is a series of statements that provide GDIF with supplemental and more specific information on how to process ENQ and RESERVE requests and hardware reserves for resources. A sample exempt list is provided in the member called GDIEXMPT in the CAI.CBTDPARM data set. The member that contains the exempt list is called the GDIEXMPT member.
exit routine
An
exit routine
is a site-defined program that is called at a predetermined time during processing. You can use exit routines to change the way
CA MIM for z/OS
and its facilities handle commands, messages, ENQ and RESERVE requests, device allocations, and resource conflicts.
externally dedicated device
An
externally dedicated device
is a device that has been given dedicated status on another system through the CA MIA VARY command. Also see dedicated status.
externally reserved device
An
externally reserved device
is a device that has been given reserved status on another system through the CA MIA VARY command. Also see reserved status.
GCMF
GCMF
is an acronym for the Global Command and Message Facility, which is available with the CA MIC component. GCMF enables you to issue cross-system commands and to collect messages from other systems.
GCMF console pool
See
console pool
.
GDIEXMPT member
The
GDIEXMPT member
is a member of the parameter data set containing statements that give GDIF supplemental information on handling ENQ and RESERVE requests and hardware reserves for specific resources. GDIF uses this member for requests only if EXEMPT=YES is specified on a QNAME statement for that class of resources. A sample member called GDIEXMPT is provided in the CAI.CBTDPARM data set. Collectively, the contents of the GDIEXMPT member are called the exempt list.
GDIF
GDIF
is an acronym for the Global Data Integrity Facility, which is available with the CA MII component. GDIF ensures integrity for shared resources by converting RESERVE requests to global ENQ requests and by propagating ENQ requests to all systems in a complex.
generic group
A
generic group
is a group of physically identical devices. z/OS creates generic groups during the system generation process. Generic groups have a critical effect on the device groups z/OS create for an allocation request.
global
The term
global
applies to all resources or processors in a shared-device, multiprocessor, or multi-image environment.
global device name
See
global name
.
global ENQ request
A
global ENQ request
is an ENQ or RESERVE request that GDIF has propagated to all systems.
global name
A
global name
is a unique name that can be used by all systems when referring to the same tape device. A global name can be three or four characters in length and may be alphanumeric or numeric. Global names are critical when a device has different unit control block names on different systems. CA MIA uses the unit control block name as the global name for a device unless you specifically assign a global name through the MIMUNITS member of the
CA MIM for z/OS
parameter data set.
GTAF
GTAF
is an acronym for the Global Tape Allocation Facility, which is available with the CA MIA component. GTAF enables you to share tape devices among systems.
hardware reserve
A
hardware reserve
is an I/O instruction that dedicates a DASD to a single processor to serialize access to one of the resources on that device. On z/OS systems, hardware reserves are produced through RESERVE requests. Also see RESERVE request.
I/O
I/O
is an abbreviation for input/output.
ICMF
ICMF
is an acronym for the Intersystem Communication Facility, which is part of the CA MIC component. ICMF enables you to route cross-system commands and messages through the CA-L-Serv communication product, rather than through CTCs or shared DASD.
image
An
image
is a logical/physical partition of a CPU that functions as a separate processing unit. A single CPU can be divided into multiple images, each operating independently and each running under a different operating system. z/VM running on an image can create further images.
inaccessible device
An
inaccessible device
is a device to which there is no physical access path, logical access path, or both.
inclusion parameters
Inclusion parameters
are parameters on the COLLECT command that tell GCMF which messages to collect. Also see exclusion parameters.
index number
See
system index number
.
ineligible device
An
ineligible device
is a device that is unavailable for allocation to the requesting job.
initialization
Initialization
is a process in which
CA MIM for z/OS
reads the startup information you have provided and stores that information for use during operations.
initialization parameters
Initialization parameters
are parameters that define elements of the
CA MIM for z/OS
operating environment that cannot be modified while it is running. You can specify initialization parameters only on initialization statements. Also see initialization statements.
initialization statements
Initialization statements
are statements that define elements of the
CA MIM for z/OS
operating environment that cannot be modified while it is running. Initialization statements are identified by the suffix INIT. Some facilities have their own initialization statements, and the initialization statement named MIMINIT influences all facilities.
initialization values
Initialization values
are elements of the
CA MIM for z/OS
operating environment that are defined through initialization statements. You cannot change these values while
CA MIM for z/OS
is running.
initiator
An
initiator
is a z/OS started task that selects jobs for execution based upon job class, scheduling priority, and other performance criteria.
integrity exposure
Integrity exposure
is a situation in which access to a resource has not been serialized, which makes it possible for that resource to be damaged.
JCL
JCL
is an abbreviation for job control language, the language used to describe the resource and execution requirements of a job to the operating system.
linkage
A
linkage
is a cross-system routing path that allows a console, product, or TSO user on the local system to issue commands to one or more external systems. Linkages also enable the issuing console, product, or TSO user to receive the cross-system responses to these commands. Linkages, which also are known as command routing paths, are created through the LINK command.
LMP codes
LMP codes
are needed to license
CA MIM for z/OS
for use at your site. These codes are placed in the KEYS member in the OPTLIB data set in the CAS9 JCL procedure.
local device name
See local name.
local name
The
local name
is a name obtained from the unit control block address for a tape device. A device may have different local names on different systems. For example, a device can have the local name 1A0 on one system and 2A0 on another system. The CA MIA application program interface and CA MIA display commands use local names when referring to devices; however, most CA MIA processing and commands use global names when referring to devices.
locally dedicated device
A
locally dedicated device
is a device that has been given dedicated status on the local system through the CA MIA VARY command. Also see dedicated status.
locally reserved device
A device that has been given reserved status on the local system through the CA MIA VARY command. Also see reserved status.
locking mechanism
A
locking mechanism
is a bit-mask that z/OS uses to serialize access to a tape device group.
managed device
A
managed device
is a tape device that CA MIA is managing. You can tell CA MIA to manage a device by specifying the local name of that device in a device control list. You also can tell CA MIA to manage an entire class of devices, such as all tape devices, by specifying the appropriate value on the DEVCLASS parameter on the MIMINIT statement.
managed resource
A
managed resource
is a resource that GDIF, ECMF, or both are managing. You can tell GDIF, ECMF, or both to manage a resource by specifying the QNAME for that resource in your QNAME list.
master system
A
master system
is a designated system that manages the virtual control file when the CTCDASD or CTCONLY communication methods are active. This system must be connected physically to all other systems in your complex through Channel-to-Channel Adapters or IBM 3088-type devices. This system also must be connected logically to all other systems through CTCPATH statements.
MCS
MCS
is an abbreviation for multiple console support, the portion of the z/OS operating system that controls consoles and message traffic to consoles.
message ID
A
message ID
is a character string that identifies a message. Also called a message prefix.
message routing definition
A
message routing definition
is a rule that tells GCMF which messages to collect, the systems from which to collect these messages, and the local product, TSO user, console, or system log that is to receive these messages. Message routing definitions also are known as collection sets. You can create message routing definitions through the COLLECT command.
message type
A
message type
is a classification that tells GCMF which messages to collect. You can enter a simple list of message types to collect a broad group of messages; however, you also can collect a subset of any message type.
migration
Migration
is a process in which
CA MIM for z/OS
suspends all requests for control file services and shifts cross-system communication to another control file.
MIMCMNDS member
The
MIMCMNDS member
is a member of the parameter data set containing
CA MIM for z/OS
commands that should be executed during the initialization process. A sample member called MIMCMNDS is provided in the CAI.CBTDPARM data set.
MIMINIT member
The
MIMINIT member
is a member of the parameter data set that contains initialization statements for
CA MIM for z/OS
and its facilities. A sample member called MIMINIT is provided in the CAI.CBTDPARM data set.
MIMMSGS member
The
MIMMSGS member
is the message member for
CA MIM for z/OS
. MIMMSGS member contains
CA MIM for z/OS
Message Facility statements that are processed as part of
CA MIM for z/OS
initialization. This member is the primary message table and points to all other message tables used by
CA MIM for z/OS
. A sample MIMMSGS member is provided in the CAI.CBTDMENU data set.
MIMPARMS data set
The
MIMPARMS data set
is the parameter data set for
CA MIM for z/OS
. This data set contains members that provide the statements and commands that should be executed at startup time. The MIMPARMS data set is identified through the //MIMPARMS DD statement in the startup procedure. A sample MIMPARMS data set is provided in the CAI.CBTDPARM data set.
MIMplex
A
MIMplex
is the collection of all systems supervised by
CA MIM for z/OS
.
MIMQNAME member
The
MIMQNAME member
is the member of the parameter data set containing statements that tells GDIF and ECMF how to handle ENQ and RESERVE requests for classes of resources. A sample member called MIMQNAME is provided in the CAI.CBTDPARM data set. Collectively, the contents of the MIMQNAME member are called the QNAME list.
MIMSYNCH member
The
MIMSYNCH member
is the member of the parameter data set containing commands that should be executed at the end of the system synchronization process. The commands in this member can be
CA MIM for z/OS
, z/OS, or JES commands. A sample member called MIMSYNCH is provided in the CAI.CBTDPARM data set.
MIMTRC data set
The MIMTRC data set is the data sets that collect trace data about commands, command output, ENQ and RESERVE requests, resource conflicts, and so on.
MIMUNITS member
The
MIMUNITS member
is the member of the parameter data set containing the names of the devices that CA MIA should manage. This member also is called the device control member. Collectively, the contents of the MIMUNITS member are called the device control list.
minidisk
A
minidisk
is a logical, addressable unit of storage on a physical device. A minidisk can be an entire device (called a full-pack minidisk) or a subsection of a device.
monitor type
A
monitor type
is a code used by MCS to route a functionally related group of monitor messages to specified consoles. A monitor type is assigned to all monitor messages and some non-monitor messages; monitor types also can be assigned to consoles. MCS matches the monitor type on the message with the monitor type on the console when routing local messages. You can use monitor types to tell GCMF which messages to collect; you can also send messages to consoles based on monitor types.
multi-line message
A
multi-line message
is a group of messages that can be displayed out-of-line in a predefined display area or displayed inline as a group on a console.
multiple console support
Multiple console support
is a portion of the z/OS operating system that controls consoles and message traffic to consoles. Abbreviated as MCS.
non-specific linkage
A
not-specific linkage
is a linkage that uses a member of the console pool to execute cross-system commands. This console pool is designated through the POOL parameter on the LINK command.
non-specific volume request
A
not-specific volume request
is a tape volume request in which no particular volume is requested. Nonspecific volume requests are made by specifying DISP=(NEW) in the JCL of a job.
non-temporary volume request
A
not-temporary volume request
is a tape volume request in which the data set on that volume is saved at the end of the step. Non-temporary volume requests are made by specifying the values DISP=(KEEP), DISP=(CATLG), or DISP=(PASS) in the JCL of a job.
not-available device
A
not-available device
is a device that has been given not-available status through the CA MIA VARY command. Also see not-available status.
not-available status
A
not-available status
is a type of device status you can assign through the CA MIA VARY command. Not-available status identifies a device that should not be selected for allocation unless no other device is available.
offline device list
An
offline device list
is a list of offline devices that z/OS allocation creates for a job that cannot allocate a suitable online device. The offline device list is created for jobs in allocation recovery. This list contains the unit control block name of every offline device with the correct physical characteristics for that request.
operating values
Operating values are elements of the
CA MIM for z/OS
operating environment that are defined through commands. You can establish these operating values at startup time, and you can change operating values at any time.
overgenned device
An
overgenned device
is a device that has been given overgenned status through the CA MIA VARY command. Also see overgenned status.
overgenned status
O
vergenned status
is a type of device status you can assign through the CA MIA VARY command. Overgenned status identifies a tape unit control block address for which there is no physical device. TPCF makes z/OS ignore overgenned devices when z/OS is selecting a device for allocation.
parallel sysplex
A
parallel sysplex
is a sysplex running in a supported IBM z/OS complex, which utilizes the 976x processor and coupling facility hardware. Also see sysplex.
parameter data set
A
parameter data set
is the data set identified through the //MIMPARMS DD statement in the
CA MIM for z/OS
startup procedure. This data set contains required and optional members that provide initialization and operating values.
PDF
PDF
is the abbreviation for Program Development Facility or Portable Document Format (Adobe).
PDS
PDS
is the abbreviation for partitioned data set.
preference logic
Preference logic
is the logic in the TPCSRMXT exit routine and in job reserve and VARY PREF processing that TPCF uses to eliminate unwanted devices after z/OS allocation has eliminated unavailable devices. TPCF uses this logic to remove devices from the candidate list z/OS creates during allocation. Preference logic tells TPCF which devices you prefer to use whenever possible. TPCF never examines preference logic during allocation recovery.
preference value
See device preference value.
processing options
Processing options
are options specified on EDIF processing statements. These options determine how EDIF processes a group of data sets or a single data set.
pseudo-volume serial number
A
pseudo-volume serial number
is a value that CA MIA generates and propagates to identify the system on which a device is allocated. This value appears in the format ss=GTA, where ss is the system alias for the allocating system. z/OS displays this number only when a device is allocated on an external system.
PTF
PTF
is the abbreviation for program temporary fix.
QNAME
A
QNAME
is
an eight-byte name that identifies a class of resources (such as data sets, control blocks, and so on) on an ENQ or RESERVE request. A QNAME also may indicate what function a task will perform with that class of resources.
QNAME list
A
QNAME list
is
a series of statements that tell GDIF and ECMF how to process ENQ and RESERVE requests for classes of resources. A sample QNAME list is provided in the member called MIMQNAME in the CAI.CBTDPARM data set. The member that contains the QNAME list is called the MIMQNAME member.
read verification
Read verification
is an EDIF feature that you can use to prevent unauthorized programs from reading a data set. During read verification, EDIF verifies that a program is authorized to read the data set. If it is not, then EDIF records the violation. EDIF also abends the program to prevent the read operation if the ABEND option is in effect. You can enable this feature by specifying the ACCESSCHECK option on an EDIF processing statement.
real reserve/release processing
Real reserve/release processing
is a DASD hardware feature that serializes access among real processors by dedicating a device to one processor at a time. Real reserve/release processing is requested through a reserve channel command word, which is produced when a task or z/OS issues a RESERVE request for a resource. The hardware is released through a release channel command word.
release CCW
A
release CCW
is a channel command word that releases a device or minidisk that had been dedicated to a processor or guest system. Also see real reserve/release processing, virtual reserve/release processing.
REQUEUE feature
The
REQUEUE feature
is an ECMF feature that places a batch job on hold and returns it to the input job queue when that job requests an unavailable resource. When the requested resource becomes available, ECMF frees the job so that it can execute. The REQUEUE feature affects only batch jobs that issue requests on which the QNAME SYSDSN is specified and works only at job start.
reserve CCW
A
reserve CCW
is a channel command word that serializes access to a device or minidisk. Also see real reserve/release processing, virtual reserve/release processing.
RESERVE facility
The
RESERVE facility
is a z/OS facility that serializes access to a resource by dedicating the DASD volume on which that resource resides to the system on which the requesting task is executing. Tasks issue RESERVE requests to use this facility. Also see RESERVE request.
RESERVE request
A
RESERVE request
is a special type of ENQ request that z/OS uses to serialize access to resources that will be shared by multiple systems.
A RESERVE request contains the UCB address of the DASD on which the requested resource resides. When the task obtains access to this resource, z/OS issues an I/O instruction that dedicates the DASD to the system on which the task is executing. This I/O instruction is known as a hardware reserve.
reserved device
A
reserved device
is a device that can be allocated only by a certain job or group of jobs. You can reserve devices through the CA MIA VARY command. Also see reserved status.
reserved status
A
reserved status
is a type of device status you can assign through the CA MIA VARY command. Reserved status identifies a device that can be allocated only by a certain job or by a group of jobs.
resource
A
resource
is any part of a computer system (such as a CPU, a data set, software, and so on) that a job or task requires.
resource conflict
See conflict.
retrieval panel
A
retrieval panel
is an optional panel in the CA MIA application program interface. This panel shows you the unit control block name of all local devices and accepts the names of the devices for which you want information. A sample retrieval panel is provided in member API1PNL1 in the CAI.CBTDPENU data.
RNAME
An
RNAME
is a 1- to 255-byte name that indicates what specific resource the task that issued an ENQ or RESERVE request needs.
routing code
A
routing code
is a code MCS uses to route a functionally related group of messages to the appropriate consoles, TSO sessions, logs, and so on. Routing codes are assigned to many, but not all messages; routing codes are also assigned to consoles and TSO users. To determine where to route messages, MCS matches the routing code on the message with the routing code assigned to a console or TSO user.
You can use routing codes to tell GCMF which messages to collect. You also can send messages to consoles based on routing codes. EDIF uses routing codes to determine which consoles and TSO sessions should receive messages about update violations, read violations, attribute violations, and data set conflicts.
routing definition
See message routing definition.
routing path
See command routing path.
serialization
Serialization is a process that controls access to resources to ensure resource integrity. Tasks can perform serialization themselves, or they can invoke the z/OS ENQ or RESERVE facilities to perform serialization. Also see ENQ facility and RESERVE facility.
service cycle
A
service cycle
is a designated length of time that
CA MIM for z/OS
waits before accessing its control file automatically. The length of a service cycle is the product of the values for the INTERVAL and CYCLES parameters on the SETOPTION command.
service interval
A
service interval
is a designated length of time that
CA MIM for z/OS
waits before querying its global facilities (that is, GDIF, GTAF, and GCMF) for cross-system transactions. If one or more of these facilities have transactions, then
CA MIM for z/OS
accesses its control file at this time. The length of a service interval is set through the INTERVAL parameter on the SETOPTION command.
shared linkage
A
shared linkage
is a linkage in which the console pool member that serves as the target console can be used by other linkages as needed. Shared linkages are created by specifying POOL=SHARE on a LINK command.
significant characters
Significant characters are non-wildcard characters in a QNAME/RNAME string or in a job name. Blanks also are considered significant characters. GDIF uses significant characters to determine the order in which to examine LOCAL and GLOBAL statements that you have specified in your exempt list.
SMF
SMF
is an abbreviation for the IBM System Management Facilities.
source system
A
source system
is an external system from which you are collecting messages through a collection set.
specific linkage
A
specific linkage
is a linkage that uses a designated console to execute cross-system commands. This console is assigned through the UCMID parameter on the LINK command.
specific volume request
A
specific volume request
is a tape volume request in which a certain data set is requested.
statement
A
statement
is a line of text that establishes elements of the
CA MIM for z/OS
operating environment that you cannot change while it is running. You can specify statements only in members of the
CA MIM for z/OS
parameter data set. Each of these statements is read during the product initialization process.
subsystem console
A
subsystem console
is a console that has been defined to the system-one for which there is no physical device or device address. Subsystem consoles are defined during the system generation process or in a member of the SYS1.PARMLIB data set, depending on what version of z/OS you are running. GCMF allocates these consoles to execute cross-system commands issued through dedicated and shared linkages.
synchronization
Synchronization
is the process in which the systems in a complex establish contact with each other and obtain the most current information about the activities of each other.
CA MIM for z/OS
accomplishes synchronization through its control files.
sysplex
A
sysplex
is an IBM strategy for providing a single-image view of a multiple-image complex. IBM sysplex initiatives are included in MVS/ESA SP 5.2.0 and above.
system
A
system
is a logical/physical partition of a CPU that functions as a separate processing unit. A system can be a separate CPU or a unique operating system. Also see image.
system alias
A
system alias
is a unique one- to two-character name that identifies a system to
CA MIM for z/OS
. You can define system aliases through the DEFSYS statement. If you do not define aliases for your systems, then
CA MIM for z/OS
uses the index number of a system as its alias.
system ID
A
system ID
is a unique character string that identifies a system to
CA MIM for z/OS
. These are the three types of system IDs accepted: system index numbers, system names, and system aliases. Also see system index number, system name, and system alias.
system index number
A
system index number
is a unique number
CA MIM for z/OS
generates the first time it recognizes a system. It uses this number to identify the origin and destination of internal transactions.
system name
A
system name
is a unique one- to eight-character name that identifies a system to
CA MIM for z/OS
. You can assign system names through the DEFSYS statement. If you do not specifically assign a system name to a system, then
CA MIM for z/OS
uses the SMF ID of the system as its name.
target console
A
target console
is the console that is executing cross-system commands issued through a linkage. A target console is the recipient of a command; it is not the console from which the cross-system command was issued.
target system
A
target system
is the external system that is receiving and executing cross-system commands issued through a linkage.
temporary volume request
A
temporary volume request
is a tape volume request in which the data set will not be saved at the end of the step.
TPCF
TPCF
is an acronym for the Tape Preferencing and Control Facility, which is available with the CA MIA component. TPCF lets you influence device selection during the device allocation process.
trace
A
trace
is a
CA MIM for z/OS
function that maintains a log of time-stamped information.
trace data set
A trace data set is the data set that you can use to collect trace data commands. For example, command output, ENQ and RESERVE requests, and resource conflicts commands. This data set is named MIMTRC. Also see MIMTRC data set.
TSO
TSO
is an abbreviation for time-sharing option, which is the component of z/OS that allows users to create and maintain programs and data sets, run jobs, view output displays, and perform other functions online from a terminal.
TSO user ID
A
TSO user ID
is a unique character string that identifies a TSO user.
UCB
UCB
is an abbreviation for unit control block, from which the name, address, and status of a device are obtained.
UCMID
A
UCMID
is a unique number assigned to a console that identifies that console. MCS uses the UCMID to indicate where a command originated from, to route messages to specific consoles, and to route command responses to the appropriate console when you append the z/OS L parameter to a command.
update violation
An
update violation
is an update that can result in damage to a data set. This update may be performed by a program that is not authorized to update the data set, by a job that specifies DISP=SHR in its JCL, or by programs that use different naming conventions for the same data set.
utility verification
Utility verification
is an EDIF feature that you can use to prevent inappropriate programs from updating a data set. During utility verification, EDIF determines whether a program is authorized to update the data set. If it is not, then EDIF records the violation, and also abends the program to prevent the update if the ABEND option is in effect. You can enable this feature by specifying the UTILITY option on an EDIF processing statement.
virtual control file
A
virtual control file
is an area in memory that
CA MIM for z/OS
uses to communicate information among systems when CTCDASD or CTCONLY are active.
CA MIM for z/OS
directs transactions to this file. The system that manages this file is known as the master system.
virtual reserve/release processing
Virtual reserve/release processing
is a z/VM feature that serializes access among guests running under the same z/VM operating system. Virtual reserve/release processing dedicates a specified minidisk to a single guest at a time.
volser
Volser
is an abbreviation for volume serial number.
VSAM
VSAM
is an abbreviation for virtual storage access method. VSAM stores fixed- or variable-length records on a direct access storage device in sequences determined by record-specific key fields, by record number, or by the order in which records were entered.
VTOC
VTOC
is an abbreviation for volume table of contents.
wait-eligible device
A
wait-eligible device
is a device that is currently allocated, but will be available to the requesting job after the current user has de-allocated the device.
wildcard characters
Wildcard characters
are special characters that let you match a character string (such as a QNAME, RNAME, job name, pattern, or message ID) with another character string that has only some of the same characters. For example, you can use a wildcard character to match a character string that you provide with any job name that has the same prefix.
XCF communication
XCF
communication is a cross-system communication method using the IBM coupling facility hardware in a sysplex environment.
CA MIM for z/OS
uses this method to communicate control file transactions among systems in a MIMplex
z/OS
z/OS
is an operating system for IBM mainframe computers. z/OS is a renamed, repackaged, and enhanced version of the OS/390 operating system.
z/OS ENQ facility
See ENQ facility.
z/OS RESERVE facility
See RESERVE facility.
z/VM
z/VM
is a generic term for the z/VM and VM/ESA operating systems.