RRN 00358 PERIPHERAL SERVICE ROUTINES

LRLPWN02

Message Triggering Condition

Result of the execution of the following command:
CRN 00413 INITIATE-COMPOUND-DIALOGUE

Report Layout

   PERIPHERAL SERVICE ROUTINES
      (A).......................                           (B).................
                                                 (C)...........................
      -------------------------------------------------------------------------
      SRCDEV   = (1).....
      SRCFILE  = (2)..
      LOGFILE  = (3)..
      ERRMODE  = (4)..
      LOGMODE  = (5).....
      (6)..... = DATE = (7)-(8)  TIME = (9):(10)  PERIOD = (11):(12)
      SEQNBR : (13).
      STATUS : (14)
      STATUS : (15)
      NBR OF CMDS TOTAL          : (16).
      NBR OF CMDS EXECUTED       : (17).
      NBR OF CMDS WAITING        : (18).
      NBR OF CMDS NOT EXECUTED   : (19).
      NBR OF CMDS NOT AUTHORIZED : (20).
      (21)...............................................................
  REPORT REFERENCE NUMBER = 0358

Parameter Identification

Par. No. Meaning Remarks
(A) command name
(B) main execution result
(C) result part type
(1) Source device Refer to SI 013
(2) Logical file identity of the input file
(3) Logical file identity of the log file
(4) Proceeding in case of an error
ABORT If an error occurs the job is
aborted
SKIP The command which causes an error
is skipped
WAIT In case of an error the module
waits 20 minutes for an operator
response
(5) Logging mode
LOGON Log the dialogue and reports
LOGONDLG Log only the dialogue
(6) Control type
(7) Month (Jan -> Dec) Parameter (7) and (8) for the
first time scheduling date
(8) Day (01 -> 31)
(9) Hour (00 -> 23) Parameter (9) and (10) for the
first time scheduling time
(10) Minute (00 -> 59)
(11) Period in hours Parameter (11) and (12) display
the time range for one time
scheduling
(12) Period in minutes
(13) Sequence number of the started job
(14) Current status of the job will be suppressed if (15) is
used
(15) Current status of the job will be suppressed if (14) is
used
(16) Number of commands to be executed
(17) Number of executed commands
(18) Number of waiting commands
(19) Number of not executed commands
(20) Number of not authorized commands
(21) Warning text

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(14) CLOSE ERROR FOR THE INPUT FILE . . . . . . . . . . Z
(14) COMMAND ERROR . . . . . . . . . . . . . . . . . . D
(14) COMMAND NOT COMPLETED . . . . . . . . . . . . . . D
(14) COMMAND NOT RECOGNIZED . . . . . . . . . . . . . . D
(14) COMMAND OUT OF SEQUENCE . . . . . . . . . . . . . D
(14) CONTINUED WITHOUT LOG FILE . . . . . . . . . . . . Z
(14) DB ACCESS ON R-ALPHCOX FAILED . . . . . . . . . . B
(14) DB ACCESS ON R-PW-TRANS FAILED . . . . . . . . . . B
(14) DB ACCESS ON R-S12GROUP FAILED . . . . . . . . . . B
(14) DB ACCESS ON R-S12USERS FAILED . . . . . . . . . . B
(14) DB ACCESS ON R-USER-FEATURE FAILED . . . . . . . . B
(14) DEVICE OFFLINE . . . . . . . . . . . . . . . . . . K
(14) DEVICE UNAVAILABLE . . . . . . . . . . . . . . . . B
(14) DIALOGUE ABORTED . . . . . . . . . . . . . . . . . Z
(14) GET FDB ERROR OF THE INPUT FILE . . . . . . . . . B
(14) GET FDB ERROR OF THE LOG FILE . . . . . . . . . . B
(14) ILLEGAL ACCESS . . . . . . . . . . . . . . . . . . E
(14) ILLEGAL DEVICE IDENTITY . . . . . . . . . . . . . E
(14) INPUT FILE FORCE RELEASED . . . . . . . . . . . . B
(14) INPUT FILE NOT DEFINED . . . . . . . . . . . . . . E
(14) INPUT FILE NOT PRESENT . . . . . . . . . . . . . . E
(14) JOB ABORTED AS DESCRIBED IN ERRMODE . . . . . . . D
(14) JOB CANCELLED BY OPERATOR . . . . . . . . . . . . Z
(14) JOB EXECUTING . . . . . . . . . . . . . . . . . . Z
(14) JOB IN QUEUE CANCELLED BY OPERATOR . . . . . . . . Z
(14) JOB WAITING FOR EXECUTION . . . . . . . . . . . . Z
(14) LOG FILE ERROR . . . . . . . . . . . . . . . . . . B
(14) LOG FILE FORCE RELEASED . . . . . . . . . . . . . B
(14) MMC SYSTEM ERROR . . . . . . . . . . . . . . . . . A
(14) NO LOGICAL DEVICE . . . . . . . . . . . . . . . . E
(14) NO PROCESS IS RUNNING . . . . . . . . . . . . . . E
(14) NUMBER OF JOBS EXCEEDED . . . . . . . . . . . . . J
(14) OPERATOR AUTHORIZATION FAILED . . . . . . . . . . G
(14) OPERATOR PASSWORD NOT FOUND . . . . . . . . . . . F
(14) PASSWORD NOT RECOGNIZED . . . . . . . . . . . . . E
(14) PASSWORD OUT OF SEQUENCE . . . . . . . . . . . . . D
(14) PROCESSING ENDED . . . . . . . . . . . . . . . . . Z
(14) PROCESSING STARTED . . . . . . . . . . . . . . . . Z
(14) READ INPUT FILE ERROR . . . . . . . . . . . . . . B
(14) RECURSIVE CALL OF COMPOUND DIALOG . . . . . . . . H
(14) SEQUENCE NUMBER NOT FOUND . . . . . . . . . . . . E
(14) SEQUENCE NUMBER OUT OF SEQUENCE . . . . . . . . . E
(14) SUCCESSFUL . . . . . . . . . . . . . . . . . . . . Z
(14) TIME OUT . . . . . . . . . . . . . . . . . . . . . C
(14) TIMEOUT AT OPEN INPUT FILE . . . . . . . . . . . . C
(14) TIMEOUT AT READ PHYSICAL NAME . . . . . . . . . . C
(14) UNEQUIPPED DEVICE . . . . . . . . . . . . . . . . E
(14) USER GROUP NOT FOUND . . . . . . . . . . . . . . . L
(14) USER NOT FOUND . . . . . . . . . . . . . . . . . . L
(14) VOLUME NOT PRESENT . . . . . . . . . . . . . . . . E
(14) WRONG PHYS NAME OF THE INPUT FILE . . . . . . . . E
(14) WRONG PHYS NAME OF THE LOG FILE . . . . . . . . . E
(15) AUTHORIZATION CHECK IS RUNNING . . . . . . . . . . Z
(15) COMMAND NOT FOUND . . . . . . . . . . . . . . . . D
(15) COMMAND NOT FOUND IN R-TASKID . . . . . . . . . . D
(15) COMMAND NOT FOUND IN R-TASKMAP . . . . . . . . . . D
(15) DB ACCESS ON R-TASKID FAILED . . . . . . . . . . . B
(15) DB ACCESS ON R-TASKMAP FAILED . . . . . . . . . . B
(15) ILLEGAL TERMINATORS FOUND . . . . . . . . . . . . D
(15) INVALID LOGON TIME . . . . . . . . . . . . . . . . Q
(15) OVERLOAD: JOB REFUSED . . . . . . . . . . . . . . R
(15) OVERLOAD: QUEUED JOB KILLED . . . . . . . . . . . R
(15) PASSWORD EXPIRED . . . . . . . . . . . . . . . . . O
(15) TIMEOUT: REPORT NOT YET RECEIVED . . . . . . . . . N
(15) UNEXPECTED END OF FILE DETECTED . . . . . . . . . M
(15) USER LOCKED . . . . . . . . . . . . . . . . . . . P

Action Description

Action Meaning
A To decide what to do take care to the parameter (18):
  • If there is a cuple of commands executed already (the interim result

was received already), then the last job to be executed was rejected. Check whether the user was authorized to execute the command at that time or the command is syntactical correct. Correct the command or remove the command out of the command file and re-submit the compound dialogue command again.

  • If the total number of commands is equal zero the compound dialogue

manager could not be logged on sucessful. Re-submit the job after waiting a while. If unsuccessful with the same fault again, call a system specialist for a fault clearing. After successful maintenance activity re-submit the job.

B Pay attention to the error messages, re-submit the job if the occasion arises and, if necessary cause a fault clearing.
C Re-submit the job after a while.
D Correct the input file and re-submit the job.
E Check the input data. If necessary, correct the input data and re-submit the job.
F Re-submit the job from the correct VDU.
G Check the input data. Remove the commands, to which the user has no access/authorization out of the input file and re-submit the job.
H Remove the command "INITIATE-COMPOUND-DIALOGUE" and/ or "CONTROL-COMPOUND-DIALOGUE" out of the input file and re-submit the job.
J Re-submit the job after another compound dialogue job has ended.
K Switch device online and re-submit the job.
L Define user or user group and re-submit the job.
M The last command in the input file does not end with a semikolon or a ASCII-input terminates not correctly. Correct the input file and re-submit the job.
N The final result of the last command is not received within 20 minutes. Remove commands which are not sending the final result within the time frame from the input file. The error is caused by the last command logged in the log file, if logging is switched on. Re-submit the job after corrections are made.
O The compound dialogue manager could not be logged on sucessfully, because the user password is not valid any more. Change your own password and re-submit the job.
P The compound dialogue manager could not be logged on sucessfully, because the user was locked in the meantime. The user has to be reset by the security officer. Re-submit the job subsequently.
Q The compound dialogue manager could not be logged on sucessfully, because the user was unwarranted to submit commands at that time. Change either the allowed access time frame of the user or re-submit the job within the allowed access time frame.
R Wait until end of overload is reported. Then re-submit the job.
Z No action is necessary.