RRN 06196 COLLECTION OF NED-TABLES

FDV6RU04

Message Triggering Condition

The report is a result of a customer request by the following command:
CRN 6651 COLLECT-NED

This report is printed out at the begin resp. at the end of collection of a Network Element Data table (NED). This report is also used to print out the actual status of collection process and internal errors.

Report Layout

 SWA-SUBSEC BULK DATA HDL
    (A).......................                   (B).................
    -----------------------------------------------------------------
        (1)....
        CONTAINS ERROR INFORMATIONS IN CASE OF ERROR(2)
        TABLE : (3).....   WAIT : (4) MIN (5) SEC    CMPTYPE: (7).....
        EXPECTED COLLECTION TIME : (8) HOUR (9) MIN (10) SEC
        CURRENT DATE/TIME             : (12)/(13)/(14)  (15):(16):(17)
        PREVIOUS COLLECTION DATE/TIME : (18)/(19)/(20)  (21):(22):(23)
        LOGICAL FILE ID   : (24).
        LOGICAL DEVICE ID : (25).
        VIRTUAL FILE :
        (26)............................................................
        NUMBER OF COLLECTED LINES    : (27)......
        NUMBER OF STORED DATABUFFERS : (28).
        JOB SEQ NBR : (29)........
        INFO : (30)......................................................
        DB RESULT : (31)...... / (32).. / (33)................................
        I/O RESULT : (34)...... / (35)...... / (36)....................
                                                            NUMBER OF
        TABLE       JOB SEQ NBR     STATUS                  LINES
        --------------------------------------------------------------
        (40)....    (41)........    (42)................    (43)....
  REPORT REFERENCE NUMBER = 6196

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(1) Command START,STOP,STATUS
(2) Errorindicator
(3) Name of NED-table e.g. HOCAL
(4) MINUTE Wait time
(5) SECOND Wait time
(7) Compression type e.g. CMPTYPE1
(8) HOUR Expected collection hours
(9) MINUTE Expected collection minutes
(10) SECOND Expected collection seconds
(12) YEAR Current year
(13) MONTH Current month
(14) DAY Current day
(15) HOUR Current hour
(16) MINUTE Current minute
(17) SECOND Current second
(18) YEAR Previous collection year
(19) MONTH Previous collection month
(20) DAY Previous collection day
(21) HOUR Previous collection hour
(22) MINUTE Previous collection minute
(23) SECOND Previous collection second
(24) Logical diskfile identity e.g. 4050
(25) Logical device identity e.g. 10181
(26) Virtual name of file
(27) Number of collected lines
(28) Number of stored databuffers
(29) Job sequence number
(30) Information line
(31) Name of relation
(32) Type of database access
(33) Result of database access
(34) Action of I/O-system
(35) Main state of I/O-system
(36) Sub state of I/O-system
(40) Name of NED-table
(41) Job sequence number
(42) Status of collection
(43) Total number of collected lines

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(30) COLLECTED WITH ERRORS . . . . . . . . . . . . . . M14
(30) COLLECTION ABORT BECAUSE OF UNRECOVERABLE ERRORS . M12
(30) COLLECTION STOPPED BY DATACOLLECTOR . . . . . . . M13
(30) COLLECTION STOPPED BY OPERATOR . . . . . . . . . . M5
(30) DATABASE ERROR . . . . . . . . . . . . . . . . . . M19
(30) DATACOLLECTOR PROCESS ERROR . . . . . . . . . . . M8
(30) FMM PROCESS ERROR . . . . . . . . . . . . . . . . M7
(30) I/O-ERROR . . . . . . . . . . . . . . . . . . . . M20
(30) NO ANSWER FROM DATACOLLECTOR . . . . . . . . . . . M11
(30) NO ANSWER FROM I/O-SYSTEM . . . . . . . . . . . . M21
(30) NO ANSWER FROM Q-ADAPTER . . . . . . . . . . . . . M38
(30) NO ANSWER FROM VFS AFTER FILE REQUEST . . . . . . M17
(30) NO ANSWER FROM VFS AFTER FILE RETURN . . . . . . . M18
(30) NO DATA AVAILABLE FOR THIS TABLE . . . . . . . . . M22
(30) NO HEADLINES PRESENT . . . . . . . . . . . . . . . M39
(30) REPEATED PROCESS ERROR . . . . . . . . . . . . . . M9
(30) RESTART OF CONTROL ELEMENT . . . . . . . . . . . . M10
(30) TABLE ALREADY STARTED . . . . . . . . . . . . . . M1
(30) TABLE ALREADY STOPPED . . . . . . . . . . . . . . M3
(30) TABLE IN QUEUE . . . . . . . . . . . . . . . . . . M2
(30) TABLE NOT WORKING . . . . . . . . . . . . . . . . M4
(30) UNABLE TO CREATE PROCESS . . . . . . . . . . . . . M6
(30) VFS-FILE ALLOCATED TO ANOTHER USER . . . . . . . . M34
(30) VFS-FILE REQUEST COMBINATION NOT ALLOWED . . . . . M31
(30) VFS-FILE REQUEST COMBINATION NOT POSSIBLE . . . . M33
(30) VFS-FILE REQUEST COMBINATION NOT SUPPORTED . . . . M30
(30) VFS-FILE UNKNOWN . . . . . . . . . . . . . . . . . M24
(30) VFS-FILE USED BY OTHER USER . . . . . . . . . . . M23
(30) VFS-INVALID FILE REQUEST COMBINATION . . . . . . . M29
(30) VFS-NO FILE REQUEST SPECIFIED . . . . . . . . . . M27
(30) VFS-SPECIAL FILE REQUEST UNKNOWN . . . . . . . . . M25
(30) VFS-TO MUCH FILEREQUESTS . . . . . . . . . . . . . M28
(30) VFS-UNEXPECTED RESULT . . . . . . . . . . . . . . M37
(30) VFS-UNKNOWN JOB REFERENCE . . . . . . . . . . . . M35
(30) VFS-UNKNOWN RESULT . . . . . . . . . . . . . . . . M36
(30) VFS-UNKNOWN USER IDENTIFICATION . . . . . . . . . M32
(30) VFS-USER DATA ERROR . . . . . . . . . . . . . . . M26
(30) WAIT TIME NOT TERMINATED . . . . . . . . . . . . . M16
(30) WRONG BUFFERSEQUENCE . . . . . . . . . . . . . . . M15

Action Description

Action Meaning
M1 The collection process is already running. You are able to find out the actual collection status with the help of the parameter "STATUS".
M10 Internal error detected. The control element was initialized. Attention! The collection processes of running tables are interrupted.
M11 The datacollector is not reachable. Possible reason: the control element was initialized. Start the collection again.
M12 An error was detected by datacollector. The collection process was stopped. Refer to the previous printed error reports.
M13 The collection process was stopped because of internal problems. Possible reason: the capacity of the control element has reached. Start the collection again to a later point of time.
M14 Errors detected during datacollection. To get more infomation about these errors you have the possibility to start the collection again with the parameter "ERRINF".
M15 A databuffer was transfered in a wrong sequence. Start the collection again. If the same error occurs again inform a system specialist.
M16 The time, after the collection of this table can be started again, is not reached. Start the collection again to a later point of time.
M17 An error occurs during the VFS file request. Start the collection again to a later point of time. If the same error occurs again inform a system specialist.
M18 An error occurs during VFS file return. Inform a system specialist.
M19 The programm interrupts its work because of an DB error. Inform a system specialist.
M2 The number of tables which can be collected in parallel is limited. In this case the new table is queued and will be started automatically after the retrieve of an other table has finished.
M20 An error was detected by the I/O-system. Start the collection again. If the same error occurs again inform a system specialist.
M21 No answer received from I/O-system. Start the collection again to a later point of time. If the same error occurs again inform a system specialist.
M22 No data available for this table.
M23 The requested virtual file is used by another user. You are able to find out this user with the help of the MMC command "DISPLAY-ACT-ATTR". Start the collection again to a later point of time.
M24 The requested VFS-filename is unknown. With the help of the MMC command "DISPLAY-VF-ATTR" it is possible to find out if this virtual file exists. If necessary inform a system specialist.
M25 Unknown VFS filerequest. Inform a system specialist.
M26 An DB error was detected in the VFS interface. Check the data with the help of the MMC commands "DISPLAY-VFS-ATTR" and "DISPLAY-ACC-AUTH".
M27 No VFS file requested by user. Inform a system specialist.
M28 Too many VFS files requested by user. Start the collection again to a later point of time. If the same error occurs again inform a system specialist.
M29 The combination of VFS file request is invalid. Inform a system specialist.
M3 The table was already stopped. With the help of the parameter "STATUS" you are able to find out the status of the collection process.
M30 The combination of VFS file request is not supported. Inform a system specialist.
M31 The combination of VFS file request is not allowed. Inform a system specialist.
M32 Unknown VFS user identification. Inform a system specialist.
M33 The combination of VFS file request is not possible. Inform a system specialist.
M34 The requested virtual file is used by another user. It is possible to find out this user with the help of the MMC command "DISPLAY-ACT-ATTR".
M35 Unknown VFS referencenumber. Inform a system specialist.
M36 The error-message received from the VFS is unknown. Inform a system specialist.
M37 The error-message received from VFS can not be classified. Inform a specialist.
M38 No answer received from Q-adapter. Check the connection to the external system (BFU).
M39 No headlines received from the specified datacollector. Inform a system specialist.
M4 The action for this table can not be executed because no collection process is running.
M5 The collection process was stopped by operator.
M6 The collection process can not be created. The capacity of control element has reached. Start the collection again to a later point of time.
M7 The program stopped because of an error. Possible reason: the capacity of the control element has reached. Start the collection process again. If the same error occurs again inform a system specialist.
M8 The datacollector was not able to create a collection process. Possible reason: the capacity the of control element has reached. Start the collection again to a later point of time.
M9 No data from datacollector received after two attemps. Possible reason: the capacity of the control element has reached. Start the collection again to a later point of time. If the same error occurs again inform a system specialist.