Skip to main content

New Page

Partition

  • The partition name as defined on the hardware console.
  • The partition identified by the name PHYSICAL is not a configured partition. Data reported in this line includes all of the
    uncaptured time which was used by LPAR but could not be attributed to a specific logical partition.
  • The summary lines like *CP or *ICF show the totals for the displayed CPU type.

Capping Option

  • The capping option of the partition (YES, MIX or NO). This field indicates whether the operator has set 'capped=yes' in the logical partition controls for the partition.
  • MIX is set by RMF, if either a non­IBM processor belongs to this partition which is not managed by the logical partition
    controls or if the capping status is currently changing.

Jobname

  • The name of the Job, the TSO Userid, the name of the started task or the name of an USS address space.

ASID

  • The address space id of a Job, TSO Userid, started task or USS address space. Unless otherwise indicated RMF
    displays the ASID number in decimal and not in hexadecimal notation.

Type

  • The type of address space:
    • B - Batch job (JES)
    • T - TSO user
    • S - Started task
    • O - USS address space (OMVS)

Service Class

  • The WLM service class that has been assigned to this address space.

Period

  • The WLM service class period that has been assigned to this address space.

Group Name

  • The name of the XCF group.

Member Name

  • The name of the XCF member or *ALL for the group summary.

Status

  • The status of the XCF member:
    • A - Active
    • C - Created
    • M - Missing
    • Q - Quiesced
    • F - Failed
    • R - Monitor Removed
    • T - Sys Termination

Status Checking Interval

  • The number of seconds that can elapse before the user status routine is scheduled. It is specified by the joining
    member by means of the STATEXIT and INTERVAL parameters.

System Name

  • The system name where this XCF member resides.

Job Name

  • JOB, STC, MOUNT, or LOGON name that joined this member.

Line Type

  • G - Group summary line
  • M - Member line

System Pair

  • For outbound requests:
    • The first name is the system from which the signals are sent. The second name is the system
      on which the signals are received.
  • For inbound requests:
    • The first name is the system on which the signals are received. The second name is the system
      from which the signals are sent.

System(1)

  • For outbound requests:
    • The name of the system from which the signals are sent.
  • For inbound requests:
    • The name of the system on which the signals are received.

System(2)

  • For outbound requests:
    • The name of the system on which the signals are received.
  • For inbound requests:
    • The name of the system from which the signals are sent.

CFStructure or CTC Device Pair

  • CTC - the device number pair being used as path
  • STR - the coupling facility structure name
  • LST - the coupling facility structure name and list number

Path Type

  • CTC - Channel to Channel
  • STR - Coupling Facility Structure
  • LST - List within Coupling Facility Structure

Transport Class

  • The name of the transport class XCF uses for message transfer.

Status

  • The status of the signalling path:
    • ST - Starting
    • RS - Restarting
    • WR - Working
    • PP - Stopped
    • WC - WaitingForComp
    • NO - NotOperational
    • FL - Failed
    • RB - Rebuilding
    • QG - Quiescing
    • QD - Quiesced

Path direction

  • O - Outbound
  • I - Inbound

Direction

  • L - Local
  • O - Outbound
  • I - Inbound

System Name

  • The name of the z/OS image in the Sysplex.

SMF Id

  • The SMF system Id.

Partition Name

  • The name of the partition where this system runs.

System Level

  • The z/OS release level running on this system.

Monitoring Interval

  • Length of time in hundredths of seconds it takes XCF to detect a failure in the Sysplex (as specified by the INTERVAL
    parameter in the COUPLExx parmlib member).

Operator Interval

  • Length of time in hundredths of seconds it takes XCF to notify the operator of a failure in the Sysplex (as specified by the OPNOTIFY parameter in the COUPLExx parmlib member).

Status

  • The status of the z/OS image:
    • A - Active
    • R - Removed
    • M - Missing
    • L - Local
    • C - Cleanup
    • U - Unknown

RMF Master

  • The indication whether this system is the RMF master.

Storage Group Name

  • Name of the storage group connected to the system.
  • The line showing *ALL in this column presents the accumulated values or average percentage values for all storage groups.

Total Capacity (MB)

  • Total amount of disk space (in megabytes) on all online volumes in the storage group.

Free Space (MB)

  • Total amount of free disk space (in megabytes) on all online volumes in the storage group.

Free Space %

  • Percentage of free disk space in the storage group.

Number of Volumes

  • Number of volumes in the storage group.

Unallocated Volumes

  • If at least one volume in the storage group did not return any space information, this is indicated by an *.

Volume

  • Name of the volume.

Total Capacity (MB)

  • Total amount of disk space (in megabytes) on the volume.

Free Space (MB)

  • Total amount of free disk space (in megabytes) on the volume.

Free Space %

  • Percentage of free disk space on the volume.

Largest Block (MB)

  • Largest block (extent) in megabytes of unallocated disk space available on the volume.

Storage Group Name

  • Name of the storage group to which the volume belongs.

Aggregate Name

  • Name of the zFS aggregate which is the name of the VSAM Linear Data Set (VSAM LDS) that contains one or more file
    systems.

File System Name

  • Name of the file system or USS file system name.

File System Values

  • All file system information concatenated into one single string. Please consult the other table column helps for more
    information.

Indicator

  • Indicator for file system ("F") or mount point ("M").

Mode

  • Mount mode of the file system:
    • R/W - Mounted in read­write mode.
    • R/O - Mounted in read­only mode.
    • N/M - Not mounted.
    • QSC - Not available because the aggregate is quiesced.

Quota Limit

  • Maximum logical size of the file system.

Quota Usage

  • Percentage of the quota currently used by the file system.

Operation Rate

  • Number of vnode operations per second on this file system.

Mount Point

  • Mount point of the file system.

Aggregate Size

  • Size of the zFS aggregate.

%Aggregate Use

  • Percentage of space used in the aggregate.

Aggregate Mode

  • There are two types of aggregates: A compatibility mode aggregate contains a single zFS file system. A multi­file
    system aggregate contains more than one zFS file system. An aggregate can have one of the following modes: 
    • R/O CP - Compatibility mode aggregate attached read­only.
    • R/W CP - Compatibility mode aggregate attached read­write.
    • R/O MS - Multi­file system aggregate attached read­only. All file systems in this aggregate are read­only and can only be mounted read­only.
    • R/W MS - Multi­file system aggregate attached read­write. The file systems in this aggregate can be mounted read­only and read­write.

Number of File Systems

  • Number of file systems in the aggregate.

Aggregate Read Rate

  • Data transfer read rate in bytes/second for the aggregate.

Aggregate Write Rate

  • Data transfer write rate in bytes/second for the aggregate.

CHPID

  • Hexadecimal number of the channel path identifier (CHPID).

Type

  • Type of channel path.
  • You may issue the console command D M=CHP(xx) to see an explanation of the channel path type. If the field is blank, RMF encountered an error collecting data. Check the operator console for messages.

Shared

  • The indication of whether a channel path is defined as shared between one or more logical partitions. Y indicates that
    the channel path is shared.

LPAR MSGRate

  • Rate of messages sent by the partition.

LPAR MSGSize

  • Average size of messages sent by the partition (in bytes).

Total MSGRate

  • Rate of messages sent by the entire system.

Total Receive Fail

  • Rate of messages (received by the entire system) that failed due to unavailable buffers.

Total MSGSize

  • Average size of messages sent by the entire system (in bytes).

FICON Operation Rate

  • Number of native FICON operations per second.

FICON Operations Active

  • Average number of native FICON operations that are concurrently active.

FICON Deferred Operation Rate

  • Number of deferred FICON operations per second. This is the number of operations that could not be initiated by the channel due to the lack of available resources.

zHPFOperation Rate

  • Number of native zHPF (High Performance FICON) operations per second.

zHPFOperations Active

  • Average number of native zHPF (High Performance FICON) operations that are concurrently active.

zHPFDerferred Operation Rate

  • Number of deferred zHPF (High Performance FICON) operations per second. This is the number of operations that could not be initiated by the channel due to the lack of available resources.

Resource

  • The resource name of the lock.

Jobname

  • The name of the address space, which is spinning due to the lock request.

Type

  • The indication, whether the lock is held exclusive or shared.

ASID

  • The decimal address space identifier of the spinning job.

CPUID

  • The identifier of the logical CPU holding the lock.

Address

  • The address of the instruction which obtained the lock.

%Held

  • The percentage of samples where the address space held the lock during the report interval.

%Spin

  • The percentage of samples where the requesting address space has been found spinning due to the unavailable lock.

Lock Type

  • The type of the suspend lock:
    • L - Local Suspend Lock
    • LX - Cross­Memory Local (CML) Suspend Lock
    • G - Global CMS Suspend Lock

Jobname

  • The name of the job/address space which holds the lock.

ASID

  • The decimal address space identifier of the job/address space which holds the lock.

%Interrupted

  • The percentage of samples where the address space was interrupted while holding the lock.

%Dispatchable

  • The percentage of samples where the address space was dispatchable while holding the lock.

%Suspended

  • The percentage of samples where the address space was suspended while holding the lock.

%channel path partition utilization

  • The channel path utilization percentage for an individual logical partition. RMF uses the values provided by CPMF (Channel Path Measurement Facility).
  • In LPAR mode, the calculation is: % partition utilization = (CBT / CET) * 100
    • CBT - Cumulative channel path busy time
    • CET - Cumulative channel path elapsed time
  • In BASIC mode, no data are shown.

%channel path total utilization

  • The channel path utilization percentage for the entire system during an interval.
  • For shared channels in LPAR mode, or for all channels in BASIC mode with CPMF not available, the calculation is:
    % total utilization = (SCB / N) * 100
    • SCB - Number of SRM observations of channel path busy
    • N - Number of SRM samples
  • For unshared channels in LPAR mode, the value for total utilization is the same as partition utilization.
  • For all channels in BASIC mode with CPMF available, the calculation is: % total utilization = (CBT / CET) * 100
    • CBT - Cumulative channel path busy time
    • CET - Cumulative channel path elapsed time

%enqueue delay

  • The percentage of time during the report interval that the system or job was waiting to use a serially reusable resource that another system or job was using.

%HSM delay

  • The percentage of time during the report interval that the system or job was waiting for services from the Hierarchical
    Storage Manager (HSM).
  • A high HSM delay value might be caused by one or more of the following:
    • HSM address spaces delayed
    • Delay on HSM volumes (Check HSM device volumes)
    • HSM doing its housekeeping during prime time
    • Not enough primary or level one space
    • HSM dispatching priority too low.


%JES delay

  • The percentage of time during the report interval that the system or job was waiting for services from the Job Entry
    Subsystem (JES).
  • A high JES delay value might be caused by one or more of the following:
    • JES address spaces delayed
    • Delay on JES volumes (Check JES device volumes)
    • JES dispatching priority too low.

%operator delay

  • The percentage of time during the report interval that the system or job was waiting for the operator to reply to a message or mount a tape, or the address space was quiesced by the operator.

%processor delay

  • The percentage of time during the report interval that the system or job or enclave was waiting for a processor.

 

  • A high processor using value might be caused by one or more of the following:
    • looping user
    • high dispatching priority for a processor­bound job (in compatibility mode) or high importance for the service class of a processor­bound job (in goal mode)
    • small block size I/O
    • excessive use of expensive supervisor service

 

  • A high processor delay value might be caused by one or more of the following:
    • ineffective choice of dispatching priorities in either the SRM IPS (compatibility mode) or ineffective choice of importances in the active service policy (goal mode)
    • high priority work using an excessive amount of CPU
    • ineffective mean­time­to­wait usage


%storage delay

  • The percentage of time during the report interval that the system or job was waiting for a COMM, LOCL (both include shared pages), SWAP, or VIO page, was on the out/ready queue, or was a result of a cross­memory address space or standard hiperspace paging delay.
  • For enclaves, only COMM, cross­memory, and shared page delays apply.
  • A high storage delay value can be associated with common storage paging (COMM), local storage paging (LOCL), swap­in delay (SWAP), swapped out and ready delay (OUTR), and other delays (OTHR) which includes virtual I/O paging and paging delays from cross­memory address spaces and standard hiperspaces.

 

  • A high storage delay associated with common storage paging might be caused by one or more of the following:
    • insufficient page data sets
    • not enough central storage
    • poorly tuned paging configuration
    • too many address spaces in storage
    • too many "logical swap" address spaces in storage
    • excessive storage isolation of address spaces
    • too many extremely large address spaces resident
    • paging data set on shared device
    • high use of user I/O on paging volume
    • "common I/O" contends with "swap I/O"
    • common data set on wrong device

 

  • A high storage delay associated with local storage paging might be caused by one or more of the following:
    • insufficient page data sets
    • not enough central storage
    • address space is under isolated (causing trim) or over isolated (causing others to page/swap)
    • poorly tuned paging configuration
    • too many address spaces in storage
    • too few (artificially low) address spaces in storage
    • too many "logical swap" address spaces in storage
    • paging data set on shared device
    • high use of user I/O on paging volume
    • too much swapping
    • page­ins are from trimming at swap­out
    • "local I/O" contends with "swap I/O"
    • program pages in each address space rather than in PLPA
    • too many extremely large address spaces resident

 

  • A high storage delay associated with virtual I/O might be caused by one or more of the following:
    • insufficient page data sets
    • poorly tuned paging configuration
    • paging data set on shared device
    • high use of user I/O on paging volume
    • virtual I/O contending with swap I/O

 

  • A high storage delay associated with swap­-in activity might be caused by one or more of the following:
    • too much swapping
    • workload too heavy
    • insufficient page/swap data sets
    • misplaced page/swap data sets
    • swap data sets on slow devices
    • too few (artificially low) address spaces in storage
    • paging data set on shared device
    • high use of user I/O on paging volume
    • swapped pages moved to backing store on cached device
    • not enough central storage

 

  • A high delay value for address spaces that are swapped out and ready might be caused by one or more of the following:
    • too few (artificially low) address spaces in storage
    • workload too heavy
    • unbalanced workload
    • not enough central storage
    • poorly tuned paging configuration
    • insufficient page/swap data sets
    • too many address spaces in storage
    • too many or too few logical swap address spaces
    • paging/swapping too slow
    • exchange swap rate too high
    • too many detected wait swaps
    • improper use of storage isolation

 

  • Other storage delays might be caused by one or more of the following:
    • paging delays from cross­memory address spaces
    • paging delays from standard hiperspaces (but not ESO hiperspaces)

% subsystem delay

  • The percentage of time during the report interval that the system or job was waiting for services from

    • Job Entry Subsystem (JES)

    • Hierarchical Storage Manager (HSM)

    • Cross-System Coupling Facility (XCF)

% XCF delay

  • The percentage of time during the report interval that the system or job was waiting for services from the Cross-System Coupling Facility (XCF).
  • A high XCF delay value might be caused by one or more of the following:

    • Path capacity exceeded.

    • Other applications are tying up the path.

    • XCF delays on the receiving system.

    • Some data paths are unavailable or offline.

% total delay

  • The percentage of time during the report interval that the job was not using any resources and was delayed for at least one of the following resources:
    • processor - the job had ready work on the dispatching queue.
    • storage - the job was delayed by paging, swapping or virtual input/output (VIO) activity, or was on the out/ready queue.
    • device - the job was waiting for a DASD or tape.
    • Job Entry Subsystem (JES)
    • Hierarchical Storage Manager (HSM)
    • Cross - System Coupling Facility (XCF)
    • OPER - the job was waiting for the operator to reply to a message or to mount a tape, or the address space was quiesced by the operator.
    • ENQ - the job was waiting to use a serially reusable resource that another job was using.

Note: If a job with several tasks is simultaneously delayed for more than one resource, RMF counts this job only once as delayed when it calculates delay percentage.

% idle

  • The percentage of time during the report interval that the system or job was idle.
  • RMF considers a job idle if it is in terminal wait, timer wait, or is waiting to be selected by JES, and it is not using or waiting for any resource that RMF monitors.

% using

  • The percentage of time during the report interval that the system or job was using one or more processors or devices.

Note: If a job with more than one task is simultaneously using and delayed for the same resource, RMF counts the job once as using and once as delayed (regardless of how many times it is found using and delayed). If a job is delayed for more than one resource, it is counted once for the overall delay and once for each resource causing a delay.

% workflow

  • Workflow percentage is the speed at which a job is moving through the system in relation to the maximum speed at which it could move through the system.
  • A low workflow percentage indicates that the job has few of the resources it needs and is contending with other jobs for system resources. A high workflow percentage indicates that the job has the resources it needs to execute and is moving through the system at a relatively high speed.
  • For example, a job that could execute in one minute if all the resources it needed were available, would have a workflow of 25 percent if it took four minutes to execute.

% unknown

  • RMF considers the system or jobs that are not delayed for a monitored resource, not using a monitored resource, or not in a monitored idle state to be in an unknown state.
  • The value represents the percentage of time during the report interval that the job was in the system, but not in any monitored state.
  • Examples of address spaces in an unknown state include those waiting for devices other than DASD or tape and those that are waiting for work (idle) using a method that RMF does not recognize. Started tasks (STCs) are usually found in this category.

% connect time

  • The sum of the percentages of time during the report interval that devices used by the job were connected to channel path(s) to transfer data between the devices and central storage.
  • Because a job can be connected to more than one device at a time, the value in connect time percentage can be greater than 100%.

Note: This can include devices other than DASD and tape; for example, graphic displays.

% using

  • The percentage of time during the report interval that one job or all jobs in a group or in the system were using one or more devices.
  • RMF considers a job to be using a device as soon as the job's I/O request is queued in the channel for the device.
  • Therefore, the using percentage for a device includes both active time on the device and queuing delay in the channel.

i/o activity rate

  • The rate per second that I/O instructions (SSCH, RSCH, and HSCH) to a device completed successfully.

IOS queue time

  • The average number of milliseconds an I/O request must wait on an IOS queue before an SSCH instruction can be issued. A delay occurs when a previous request to the same subchannel is in progress.

response time

  • The average response time (in milliseconds) that the device required to complete an I/O request.

i/o intensity

  • The product of the number of users and the time waiting in average for a DASD device because of one of the following reasons:

    • The path and device are busy

    • The SIO is pending

    • The device is busy

    • The SIO is queued

Note: there is no common name for I/O intensity in the literature. Other programs might use different names. The following terms are equivalent to I/O Intensity: DASD MPL, Response Time Volume.


% active time

  • The percentage of time during the report interval that the device was active.

Note: active time = connect time + disconnect time + pending time

% connect time

  • The percentage of time during the report interval that the device was connected to a channel path.

% disconnect time

  • The percentage of time during the report interval that the device had an active channel program, but was not connected to the channel.

Note: Disconnect time includes seek time, normal rotational delay time, and extra rotational delay time because the channel was busy.

% pending time

  • The percentage of time during the range period that I/O requests were waiting in a channel queue before a path was available.

Note: Pending time includes the time spent waiting for a device, a control unit, a head of string, or a channel.

% I/O delay

  • The percentage of time during the report interval that the job is waiting for any DASD or tape, or has an I/O request queued in the channel for a device, but not transmitting data (for example, is being disconnected to seek).
  • A high device delay value for a job usually means that another job has a high using value for the same device. Use the Device Delay report to determine what volume a job is waiting for; then use the Device Resource Delay report to determine how the job using that volume is spending its time.

 

  • General reasons for a high device using value might include:

    • Unnecessary I/O (such as using DASD instead of VIO for temporary data sets).

    • Data sets on a slow device.

  • Using time for a volume will approximately equal connect time (time that the device was connected to a channel path).
  • Using time does not include disconnect time (time that the device had an active channel program but was not connected to the channel) and pending time (time that I/O requests were waiting in a channel queue before a path was available).

 

  • A high connect percentage (CON %) might be caused by one or more of the following:
    • programs not resident
    • inappropriate application parameters
    • inefficient use of device by application(s)
    • not enough in-storage buffering
    • heavy BLDL activity
    • high VTOC activity

 

  • A high disconnect percentage (DSC %) might be caused by one or more of the following:
    • small block size I/O
    • multiple revolutions per I/O due to missing channel connects or reconnects
    • long seeks because of data set placement or multiple extents on high use data sets
    • heavy BLDL activity
    • high miss ratio for cached device
    • misplaced VTOC or CATALOG or both
    • channel, control unit, or head of string contention

 

  • A high pending percentage (PND %) might be caused by one or more of the following:
    • shared DASD contention
    • device not responding
    • channel, control unit, or head of string contention
    • poorly balanced I/O
    • PND time of 100 % usually means another system had the device reserved

% delay device busy

  • The percentage of time during the range period when there was an I/O request delay because the device was busy.

Note: Device busy might mean that another system is using the volume, another system reserved the volume, or a head of string busy condition caused the contention.

% control unit busy

  • The percentage of time during the range period when there is an I/O request delay because the control unit was busy. If the device is shared at the control unit level, a sharing system might be using the device. If the device is not shared at the control unit level, the contention is the result of other activity to different devices over an alternate path serviced by this control unit.

% director port busy

  • The percentage of time during the range period when there is an I/O request delay because the ES Connection Director port was busy.

% using

  • The percentage of time during the report interval that the job was using the volume.

Note: RMF considers a job to be using a device as soon as the job's I/O request is queued in the channel for the device. Therefore, the using percentage for a device includes both active time on the device and queuing delay in the channel.

% all channel paths busy

  • The percentage of time during the measurement interval when all channel paths belonging to the LCU were busy at the same time.
  • Only channel paths that are both online to the system and connected to a device are included in the calculation:
    • % all channel paths busy = CHPID0 * CHPID1 * CHPID2 * CHPID3
      • CHPIDn = Percentage busy of each channel path involved

% control unit busy

  • This value shows for each channel path of the LCU the relationship between requests deferred due to control unit busy and total successful requests serviced by that path.
  • Each CHPID of the LCU measures the distribution of control unit contention.
  • The calculation is: % control unit busy = ((CUB / (DPB + CUB + SUC)) * 100
    • DPB = Number of deferred I/O requests due to director port busy
    • CUB = Number of deferred I/O requests due to control unit busy
    • SUC = Number of successful I/O requests on that path

% director port busy

  • This field indicates director port contention.
  • It is the number of times an I/O request was deferred because the director port was busy during the measurement interval.
  • The calculation is: % director port busy = ((DPB / (DPB + CUB + SUC)) * 100
    • DPB = Number of deferred I/O requests due to director port busy
    • CUB = Number of deferred I/O requests due to control unit busy
    • SUC = Number of successful I/O requests on that path

% CHPID taken

  • The rate at which I/O requests to devices of this LCU are satisfied by each CHPID during the interval.
  • By reviewing the rate at which each channel path of the LCU satisfies I/O requests, you can see how evenly the work requests are distributed among the available paths and how effectively those paths are arranged for the LCU.
  • The calculation is: % CHPID taken = (TO / SI) * 100
    • TO - Total number of I/O operations accepted on that path
    • SI - Number of seconds in the interval

# delayed i/o requests

  • The average number of delayed requests on the control unit header (CUHDR).
  • Each time a request is enqueued from the CUHDR, RMF counts the number of requests remaining on the queue and adds that number to the accumulator.
  • The calculation is: # delayed i/o requests = (AL ER) / ER
    • AL - Accumulated queue length
    • ER - Total number of enqueued requests

delayed i/o request rate

  • The rate per second at which the IOP places delayed I/O requests on the CUHDR for this LCU. This is done when all paths to the subchannel are busy and at least one path to the control unit is busy.
  • For devices with only one path, or for devices where multiple paths exist and the busy condition is immediately resolved, the IOP does not count the condition.
  • The calculation is: delayed i/o request rate = ER / SI
    • ER - Total number of enqueued requests
    • SI - Number of seconds in the interval

% delay by volume

  • The percentage of delay caused because the job was waiting to use the named volume.

% using

  • The percentage of time during the report interval that one job or all jobs in a group or in the system were using one or more processors.

% appl (TCB + SRB) by job

  • The percentage of processor time used by the job during the report interval.
  • This metric does not include:
    • enclave CPU time - see % eappl if you want enclave CPU time included.

    • AAP processor time - see % AAP if you want to monitor AAP processor time.

Note: This metric is NOT adjusted (divided) by the number of processors.

working set

  • The working set represents the (central or expanded) storage the user has when a job is actually running. Shared page counts are not included in the working set.

% delay for SWAP

  • The percentage that swapin delays contributed to the delay of a job.

% delay for COMM

  • The percentage that common storage (common service area (CSA) or link pack area (LPA)), including shared pages, contributed to the delay of a job.

% delay for LOCL

  • The percentage that local (private) storage paging, including shared pages contributed to the delay of a job.

% delay for OTHR

  • The percentage that various types of delays contributed to the delay of a job.
  • This is the sum of:
    • VIO (virtual I/O)
    • Paging delays from cross-memory address spaces
      • For example, if the DB2 address space does not have sufficient central/expanded storage, CICS could be delayed by crossmemory page-in in the DB2 address space. This would show up as a crossmemory delay for CICS.
    • Paging delays from standard hiperspaces (but not ESO hiperspaces).
      • This delay could be caused by a job running DFSORT with hipersorting if the DFSORT hiperspace's pages were migrated from expanded to auxiliary storage.

% delay for OUTR

  • The percentage that swappedoutandready delays contributed to the delay of a job.

 

Back to top