RRN 01118 SCHEDULE ADMINISTRATION

PLKKWJ06

Message Triggering Condition

This message is triggered internal by a command started by the command scheduler.

Report Layout

   PERIPHERAL SERVICE ROUTINES
      (A).......................                           (B).................
      -------------------------------------------------------------------------
      (1)...........................................
      AREA    = (3)
      CMD     = (4).......................
      COMNBR  = (5).
      SEQNBR  = (6).
      USERID  = (7).....
      SCHEDID = (9)
      ERRMODE = (10)...
      RETRY   = (11)
      DAYTYPE = (12).....................
      STRDATE = (13)-(14)-(15)
      STRTIME = (16):(17)
      PMONTHS = (18)     PDAYS = (19)     PHOURS = (20)     PMINUTES = (21)
      PERIOD  = (22)...
      (23)......................................
  REPORT REFERENCE NUMBER = 1118

Parameter Identification

Par. No. Meaning Remarks
(A) command name
(B) main execution result
(1) Result
(3) Command area
(4) Command name
(5) Command reference number
(6) ########
(7) Userid
(9) Schedule identity
(10) Behaviour in case of error
SKIP Skip error
SUSPEND Abort schedule if error
(11) Retry in case of error
(12) Type of day
(13) Year of activation
(14) Month if activation
(15) Day of activation
(16) Hour of activation
(17) Minute of activation
(18) Period in month
(19) Period in days
(20) Period in hours
(21) Period in minutes
(22) Type of period
(23) Errormessages

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(23) ACCESS DENIED - SCHEDULE OPENED BY AN OTHER USER . J
(23) ACTIVATION TIME DELAY TOO SHORT . . . . . . . . . I
(23) COMMAND SKIPPED : ILLEGAL COMMAND ACCESS . . . . . G
(23) COMMAND SKIPPED : USER LOCKED . . . . . . . . . . G
(23) COMMAND SKIPPED : USER OR GROUP UNKNOWN . . . . . G
(23) DATABASE ACCESS FAILURE . . . . . . . . . . . . . C
(23) INTERNAL DATA INCONSISTENCY . . . . . . . . . . . H
(23) NO FREE SCHEDULE . . . . . . . . . . . . . . . . . D
(23) NO MORE SPACE IN R-CMD-UBUF . . . . . . . . . . . D
(23) NO OPEN SCHEDULE . . . . . . . . . . . . . . . . . A
(23) NO TIMER AVAILABLE . . . . . . . . . . . . . . . . C
(23) NUMBER OF ARGUMENTS FOR DATE OR TIME INCORRECT . . B
(23) PERIOD TIME TOO SHORT . . . . . . . . . . . . . . B
(23) SCHEDULE DATE OR TIME OR PERIOD INCORRECT . . . . B
(23) SCHEDULE SUSPENDED : ILLEGAL COMMAND ACCESS . . . F
(23) SCHEDULE SUSPENDED : USER LOCKED . . . . . . . . . F
(23) SCHEDULE SUSPENDED : USER OR GROUP UNKNOWN . . . . F
(23) SCHEDULE SUSPENDED: SEMANTIC ERROR . . . . . . . . E
(23) USER AUTHORIZATION COULD NOT BE DETERMINED . . . . K
(23) USER NOT AUTHORIZED FOR THIS SCHEDULE . . . . . . J

Action Description

Action Meaning
A Use one of the commands CREATE-SCHEDULE or OPEN-SCHEDULE to prepare a schedule for command entries before scheduling commands.
B Check your input and try again.
C Wait a few minutes and resubmit the command. Close or cancel the schedule after some unsuccessful attempts and contact a system-manager for error analysis.
D The limit of possible schedules is reached. Display actual schedules using the command DISPLAY-SCHEDULE and check if obsolete schedules can be deleted using the command REMOVE-SCHEDULE.
E The suspended schedule can be deleted using REMOVE-SCHEDULE or activated using ACTIVATE-SCHEDULE.
F The user who scheduled the command is unknown, locked or not allowed to execute the schedule command. The schedule can be activated, if the user gets the access right for all scheduled commands.
G The user who scheduled the command is unknown, locked or not allowed to execute the scheduled command. Therefore the actual command is skipped and the following command will be performed.
H Check if the schedule was completed correctly.
I The delay to start the schedule is to short. The delay has to be at least 3 minutes. Check your input and try again.
J The user authorization is not identical with the user authorization of the user which has created the schedule. Please lock on with the right user authorization and reenter the command.
K An access to the database system was not successful. Reenter the command after a while.