FUNL0113 Bad page trailer for (ddname), Table (t) Page (p), at cylinder (n1) track (n2): (Xtrlr DD) (Xtrlr tpg).: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
No edit summary
Line 1: Line 1:
A page was read from the indicated database ddname, cylinder and track, which was expected to be page number ''p'' of table ''t'': ('''0'''=FCT, '''1'''=Table A, '''2'''=Table B, '''3'''=Table C, '''4'''=Table D). Each <var class="product">Model 204</var> page contains a trailer that includes the file name (DD name) for the file and the <var class="product">Model 204</var> table and page number. The trailer for the page read does not match the expected values for these fields. Rather, the page trailer contained the name ''Xtrlr DD'' (shown in hexadecimal) and the table concatenated with page number was ''Xtrlr tpg'', also in hexadecimal. This could be caused by reading a database file that is being updated, or could be caused by an erroneous DD card or FILEDEF command, hardware problems, or a corrupted database file.  
A page was read from the indicated database ddname, cylinder and track, which was expected to be page number ''p'' of table ''t'': ('''0'''=FCT, '''1'''=Table A, '''2'''=Table B, '''3'''=Table C, '''4'''=Table D). Each <var class="product">Model 204</var> page contains a trailer that includes the file name (DD name) for the file and the <var class="product">Model 204</var> table and page number. The trailer for the page read does not match the expected values for these fields. Rather, the page trailer contained the name ''Xtrlr DD'' (shown in hexadecimal) and the table concatenated with page number was ''Xtrlr tpg'', also in hexadecimal. This could be caused by reading a database file that is being updated, or could be caused by an erroneous DD card or FILEDEF command, hardware problems, or a corrupted database file.  


If the error is in Table D, ensure that you are not using the UAI INVISIBLE nor UAI OINDEX statements with a file that is having the Ordered Index updated. Verify the DD card or FILEDEF command. Check your EREP logs for DASD I/O errors. Call Sirius Software Support for assistance.  
If the error is in Table D, ensure that you are not using the UAI INVISIBLE nor UAI OINDEX statements with a file that is having the Ordered Index updated. Verify the DD card or FILEDEF command. Check your EREP logs for DASD I/O errors. Call Sirius Software Support for assistance.  


If ''[[Fast/Unload]]'' is able to continue in spite of this error, one of the messages FUNL0049, FUNL0050, or FUNL0056 will follow; the action taken for these messages depends on the HARDERR parameter. If Fast/Unload is unable to continue, it will abend with a diagnostic dump.
If [[Fast/Unload]] is able to continue in spite of this error, one of the messages FUNL0049, FUNL0050, or FUNL0056 will follow; the action taken for these messages depends on the HARDERR parameter. If Fast/Unload is unable to continue, it will abend with a diagnostic dump.


[[Category:Fast/Unload Messages]]
[[Category:Fast/Unload Messages]]

Revision as of 22:20, 21 March 2013

A page was read from the indicated database ddname, cylinder and track, which was expected to be page number p of table t: (0=FCT, 1=Table A, 2=Table B, 3=Table C, 4=Table D). Each Model 204 page contains a trailer that includes the file name (DD name) for the file and the Model 204 table and page number. The trailer for the page read does not match the expected values for these fields. Rather, the page trailer contained the name Xtrlr DD (shown in hexadecimal) and the table concatenated with page number was Xtrlr tpg, also in hexadecimal. This could be caused by reading a database file that is being updated, or could be caused by an erroneous DD card or FILEDEF command, hardware problems, or a corrupted database file.

If the error is in Table D, ensure that you are not using the UAI INVISIBLE nor UAI OINDEX statements with a file that is having the Ordered Index updated. Verify the DD card or FILEDEF command. Check your EREP logs for DASD I/O errors. Call Sirius Software Support for assistance.

If Fast/Unload is able to continue in spite of this error, one of the messages FUNL0049, FUNL0050, or FUNL0056 will follow; the action taken for these messages depends on the HARDERR parameter. If Fast/Unload is unable to continue, it will abend with a diagnostic dump.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=FUNL0113_Bad_page_trailer_for_(ddname),_Table_(t)_Page_(p),_at_cylinder_(n1)_track_(n2):_(Xtrlr_DD)_(Xtrlr_tpg).&oldid=54316"