MSIR.0426 Error updating second field of related pair in (file) record (rec) (field) = (value) - FISTAT set to physically broken: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Created page with "This message indicates that an update to record number ''''rec'''' in file ''''file'''' has succeeded for a field referenced on a SIRFIELD RELATE command. When the related update...")
 
(Automatically generated page update)
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This message indicates that an update to record number ''''rec'''' in file ''''file'''' has succeeded for a field referenced on a SIRFIELD RELATE command. When the related update to ''''field''''. was attempted, it failed for some reason, which should be identified by an M204 message preceding this one.  
This message indicates that an update to record number '''''rec''''' in file '''''file''''' has succeeded for a field referenced on a SIRFIELD RELATE command. When the related update to '''''field'''''. was attempted, it failed for some reason, which should be identified by an M204 message preceding this one.  


This message is only issued if ''''file'''' does not have TBO logging active (that is, FRCVOPT has the 8 bit set). With FRCVOPT 8 on, the update to the first field will not be backed out, and so the file is physically inconsistent because an occurrence to a field has been updated while the corresponding ''''field'''' occurrence has not been updated. When this message is issued, ''''file'''' is marked physically inconsistent (FISTAT 2 bit set) and a user restart is performed.  
This message is only issued if '''''file''''' does not have TBO logging active (that is, FRCVOPT has the 8 bit set). With FRCVOPT 8 on, the update to the first field will not be backed out, and so the file is physically inconsistent because an occurrence to a field has been updated while the corresponding '''''field''''' occurrence has not been updated. When this message is issued, '''''file''''' is marked physically inconsistent (FISTAT 2 bit set) and a user restart is performed.  


You should correct the physical inconsistency by rolling back or restoring the file to a consistent state. Then, before this update can be applied, you must correct the condition which caused the update failure.  
You should correct the physical inconsistency by rolling back or restoring the file to a consistent state. Then, before this update can be applied, you must correct the condition which caused the update failure.  


Notes:  
Notes:  
<ul>
<li>If the attempted update is from the User Language <var>FILE RECORDS UNDER</var> statement or from the IFAM <var>IFFILE</var> function, '''''rec''''' will be -1.


If the attempted update is from the User Language '''FILE RECORDS UNDER''' statement or from the IFAM '''IFFILE''' function, ''''rec'''' will be -1.  
<li>If the attempted update is from the User Language <var>DELETE EACH</var> statement or from the IFAM <var>IFDALL</var> function, '''''value''''' will be <code>*NOVAL*</code>.
</ul>


If the attempted update is from the User Language '''DELETE EACH''' statement or from the IFAM '''IFDALL''' function, ''''value'''' will be ''''*NOVAL*''''.
{{Template:MSIR.0426 footer}}
 
[[Category:MSIR.0400 - MSIR.0599]]
[[Category:Sirius Mods Messages]]

Latest revision as of 23:12, 3 March 2017

This message indicates that an update to record number rec in file file has succeeded for a field referenced on a SIRFIELD RELATE command. When the related update to field. was attempted, it failed for some reason, which should be identified by an M204 message preceding this one.

This message is only issued if file does not have TBO logging active (that is, FRCVOPT has the 8 bit set). With FRCVOPT 8 on, the update to the first field will not be backed out, and so the file is physically inconsistent because an occurrence to a field has been updated while the corresponding field occurrence has not been updated. When this message is issued, file is marked physically inconsistent (FISTAT 2 bit set) and a user restart is performed.

You should correct the physical inconsistency by rolling back or restoring the file to a consistent state. Then, before this update can be applied, you must correct the condition which caused the update failure.

Notes:

  • If the attempted update is from the User Language FILE RECORDS UNDER statement or from the IFAM IFFILE function, rec will be -1.
  • If the attempted update is from the User Language DELETE EACH statement or from the IFAM IFDALL function, value will be *NOVAL*.


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