MSIR.0245 Date out of range in FILE (file) record (rec) (field) = (value): Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
 
(One intermediate revision by the same user not shown)
Line 17: Line 17:
If the attempted update is from the SOUL <var>FILE RECORDS UNDER</var> statement or from the IFAM <var>IFFILE</var> function, '''''rec''''' will be -1. For SOUL, <code>M204.1096 THERE WERE NO UPDATES FOR BACKOUT TO PROCESS</code> is also issued.
If the attempted update is from the SOUL <var>FILE RECORDS UNDER</var> statement or from the IFAM <var>IFFILE</var> function, '''''rec''''' will be -1. For SOUL, <code>M204.1096 THERE WERE NO UPDATES FOR BACKOUT TO PROCESS</code> is also issued.


[[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]]
{{Template:MSIR.0245 footer}}
[[Category:MSIR.0200 - MSIR.0399]]

Latest revision as of 23:08, 3 March 2017

This message indicates that an update to record number rec in file file for field field was attempted, and that the value being stored is outside the valid date range implied by the SIRFIELD FORMAT command for field or, if field is related to another field, to the valid date range implied by the SIRFIELD FORMAT command for the related field.

A valid date range is one of these:

  • 1900 - 2899, for a field with "three-digit years" (format contains the token CYY or ZYY)
  • the period of years of length SPANSIZE beginning at the effective year CENTSPAN, for a field with "two-digit years" (format contains the token YY).
  • 1753 - 9999, for a field with a numeric format (ND, NS, or NM).

If field or its related field has two-digit years, you may be able to increase the valid date range of the fields. You can increase SPANSIZE, and you can decrease the effective CENTSPAN, to increase the range of a two-digit year field. See the restrictions of this as described for message MSIR.0349. If you change SPANSIZE or CENTSPAN (using SIRFIELD FORMAT), you do not need to respecify the DATE clause.

If the range cannot be increased to handle the date, you can accept this value by adding an ERROR format to the SIRFIELD RELATE command for the field, or, if the field is not related, to the SIRFIELD FORMAT command.

If you maintain your SIRFIELD commands for a file reorganization, you should update those commands as well, if you change SPANSIZE or CENTSPAN or add an ERROR format. You can also simply update your set of SIRFIELD commands for the file and re-execute all of them.

If the attempted update is from the SOUL FILE RECORDS UNDER statement or from the IFAM IFFILE function, rec will be -1. For SOUL, M204.1096 THERE WERE NO UPDATES FOR BACKOUT TO PROCESS is also issued.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages