4. EXCEPTIONS › 4.3 Detailed Exception Descriptions › 06027: Scheduling Conflict Percentage Exceeds Standard

06027: Scheduling Conflict Percentage Exceeds Standard

    FILE:            IMS System Activity
    SAS FILE NAME:   DETAIL.IMSISY01
    SOURCE LOCATION: sharedprefix.MICS.SOURCE(DYIMSEXC)

    SEVERITY:        Impacting     (SEVERITY='I')
    MANAGEMENT AREA: Performance   (MGMTAREA='PERFORMANCE')

    PURPOSE:  Identifies the time period during which the
scheduling conflict percentage exceeded the installation
standard.

    RATIONALE:  Scheduling conflicts occur when the scheduler
examines an SMB in class/priority order with a message queued
that cannot be scheduled for one of the following reasons:

  o  program conflict - A transaction is already active and
                        is not eligible for parallel
                        scheduling.

  o  priority cutoff  - A transaction of higher priority in
                        this class has previously suffered
                        an intent failure schedule and that
                        transaction had scheduling option 1
                        or 2.

  o  DB intent        - The data base needed for the
                        transaction is held by another PSB
                        using PROCOPT=E or there is a pool
                        space failure in DMB PSB or PSBW.

  o  other conflicts  - These include :  The data base
                        stopped, SMB locked or stopped, PSB
                        locked or stopped, SMB is zero
                        priority, I/O error on DOPT PSB, and
                        SMB is already in the process of
                        being scheduled.

A high conflict percentage can be caused by any of the above
reasons.  DB intent conflicts are the most expensive.  BMP
SMBs should be assigned to a non-scheduleable class which
will prevent scheduling conflicts.  Resources which are
stopped or locked for long periods should also have
transactions that use them assigned to non-scheduleable
classes.  If there are a high number of program conflicts,
parallel scheduling may be considered.

    DEFINITION:  This exception is detected when the
scheduling  conflict percentage exceeds the installation-
defined limit.

    EXCEPTION STATEMENTS:  The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:

*
**  06027
**  SCHEDULING CONFLICT PERCENTAGE EXCEEDS STANDARD
*;
IF ISYPCCFL > scheduling-conflict-percent
 THEN DO;
  EXCCODE='06027'; SEVERITY='I'; MGMTAREA='PERFORMANCE';
  EXCDESC1=
  'SCHEDULING CONFLICT PERCENTAGE EXCEEDS STANDARD';
  EXCDESC2='SCHED CONFLICT PERCENTAGE = '
           || PUT(ISYPCCFL,7.2);
  LINK HIT;
END;

    THRESHOLD MODIFICATION:  Modify the value used for the
scheduling-conflict-percent.