Dictionary/204 messages: Difference between revisions
(Created page with "==Shared messages== <table class="thJustBold"> <tr> <th style="border-top: 2px solid #aaa">Number</th> <th style="border-top: 2px solid #aaa">Message text</th> </tr> <tr><th...") |
No edit summary |
||
Line 106: | Line 106: | ||
<tr><th style="border-top: 2px solid #aaa">DIC010</th><th style="border-top: 2px solid #aaa">Global variable table is full. Please exit session</th></tr> | <tr><th style="border-top: 2px solid #aaa">DIC010</th><th style="border-top: 2px solid #aaa">Global variable table is full. Please exit session</th></tr> | ||
</table> | </table> | ||
==DDGEN messages== | ==DDGEN messages== | ||
Line 156: | Line 155: | ||
==DDMIG Facility messages== | ==DDMIG Facility messages== | ||
<table class="thJustBold"> | <table class="thJustBold"> | ||
<tr> | <tr> | ||
Line 224: | Line 222: | ||
<tr class="head"><th style="border-top: 2px solid #aaa">MIG032</th><th style="border-top: 2px solid #aaa">Import failed - the listed view(s) already exist in the dictionary.</th></tr> | <tr class="head"><th style="border-top: 2px solid #aaa">MIG032</th><th style="border-top: 2px solid #aaa">Import failed - the listed view(s) already exist in the dictionary.</th></tr> | ||
</table> | </table> | ||
==Dictionary Administration messages== | ==Dictionary Administration messages== | ||
Line 464: | Line 461: | ||
==Documentation messages== | ==Documentation messages== | ||
<table class="thJustBold"> | <table class="thJustBold"> | ||
<tr> | <tr> | ||
Line 578: | Line 574: | ||
<tr><td /><td><b>Description:</b> The WIDen command is available only for entity types with a file name prefix: RECORD, FIELD, FIELD GROUP, and PROCEDURE.</td></tr> | <tr><td /><td><b>Description:</b> The WIDen command is available only for entity types with a file name prefix: RECORD, FIELD, FIELD GROUP, and PROCEDURE.</td></tr> | ||
</table> | </table> | ||
==File Management messages== | |||
<table class="thJustBold"> | |||
<tr> | |||
<th style="border-top: 2px solid #aaa">Number</th> | |||
<th style="border-top: 2px solid #aaa">Message text</th> | |||
</tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM001</th> | |||
<th style="border-top: 2px solid #aaa">On Attention was hit, use PF3 or QUIt to exit</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM002</th><th style="border-top: 2px solid #aaa">FIND CONFLICT, use PF3 to QUIt or re-enter command</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM003</th><th style="border-top: 2px solid #aaa">Correct all tagged items, press ENTER to view messages</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM004</th><th style="border-top: 2px solid #aaa">No changes have been made to the screen</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM005</th><th style="border-top: 2px solid #aaa">Widen is not a valid command for this item</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM006</th><th style="border-top: 2px solid #aaa">Invalid characters found in name</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM007</th><th style="border-top: 2px solid #aaa">Unrecognized value entered. Field reset to value.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM008</th><th style="border-top: 2px solid #aaa">Enter the field name to be copied on the command line.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM009</th><th style="border-top: 2px solid #aaa">Field not copied. Unable to locate field.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM010</th><th style="border-top: 2px solid #aaa">Valid prefix marker is 'X'</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM011</th><th style="border-top: 2px solid #aaa">Valid prefix markers are 'X' and 'D'</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM012</th><th style="border-top: 2px solid #aaa">WARN: Field name will not be modified unless you mark the prefix </th></tr> | |||
<tr><td /><td><b>Description:</b> You have modified some attribute of a field without entering an X for the prefix. If you do not enter X, your modifications will not be saved. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM013</th><th style="border-top: 2px solid #aaa">Information on line has not been completed </th></tr> | |||
<tr><td /><td><b>Description:</b> You have not entered all the required information on a line on the screen. This error can occur on one of the list screens; for example, the Record Name List screen requires that you enter the record name and the number of records for that record. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM014</th><th style="border-top: 2px solid #aaa">Cursor is not on an input item</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM015</th><th style="border-top: 2px solid #aaa">Use PF3 to cancel the DELETE | INITIALIZE COMMAND Command or PF12 to Process </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested a DELETE or INITIALIZE command and must confirm your request by using PF12 to END or PF3 to QUIT. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM016</th><th style="border-top: 2px solid #aaa">Delete requested - use PF3 to cancel request</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM017</th><th style="border-top: 2px solid #aaa">CURSOR not on valid value cycling field.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM018</th><th style="border-top: 2px solid #aaa">MIXED DBCS requires a minimum PREALLOCATED LENGTH of length bytes.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM019</th><th style="border-top: 2px solid #aaa">WARN: MIXED DBCS requires a minimum length of @1 bytes.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM020</th><th style="border-top: 2px solid #aaa">BUG: Number of datasets exceeds maximum allowed </th></tr> | |||
<tr><td /><td><b>Description:</b> File Management only allows 100 data sets to be internally contained in 1 file. Notify Technical Support. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM021</th><th style="border-top: 2px solid #aaa">BUG: An Invalid Fileorg was found on file entry </th></tr> | |||
<tr><td /><td><b>Description:</b> The Fileorg parameter in the file you are processing is not a valid Model 204 value. Notify Technical Support. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM022</th><th style="border-top: 2px solid #aaa">BUG: System error found in scrolling routine </th></tr> | |||
<tr><td /><td><b>Description:</b> There is incorrect information in the scrolling records in the M204TEMP record which has been passed from the Field List to the Field Attributes process. Notify Technical Support. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM023</th><th style="border-top: 2px solid #aaa">DBCS PREALLOCATED fixed length must be even.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM024</th><th style="border-top: 2px solid #aaa">WARN: DBCS Average length must be even.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM025</th><th style="border-top: 2px solid #aaa">Conflicting attributes ORDERED NUMERIC and MIXED/PURE DBCS.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM026</th><th style="border-top: 2px solid #aaa">Conflicting attributes RECORD SECURITY and MIXED/PURE DBCS.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM027</th><th style="border-top: 2px solid #aaa">Conflicting attributes INVISIBLE and AT-MOST-ONE.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM028</th><th style="border-top: 2px solid #aaa">Conflicting attributes CODED FLOAT and PREALLOCATED.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM029</th><th style="border-top: 2px solid #aaa">item1 has been copied to item2.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM030</th><th style="border-top: 2px solid #aaa">A '+' is an invalid character for the tagged item</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM031</th><th style="border-top: 2px solid #aaa">A '.' is an invalid character for the tagged item</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM032</th><th style="border-top: 2px solid #aaa">You must enter a name to document</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM033</th><th style="border-top: 2px solid #aaa">WARN: You have marked the prefix but have not changed the name</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM034</th><th style="border-top: 2px solid #aaa">The tagged item(s) must be an integer</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM035</th><th style="border-top: 2px solid #aaa">item has been copied.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM036</th><th style="border-top: 2px solid #aaa">At last field.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM037</th><th style="border-top: 2px solid #aaa">At first field.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM038</th><th style="border-top: 2px solid #aaa">NUMERIC VALIDATION must be selected with 1NF.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM039</th><th style="border-top: 2px solid #aaa">DISABLE TBO must be selected with APPLY UPDATES DURING RF.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM090</th><th style="border-top: 2px solid #aaa">BUG: No entry was found for entity entryname </th></tr> | |||
<tr><td /><td><b>Description:</b> The system has encountered a dictionary reference that has a missing entry record in METADATA. Contact your Dictionary Administrator. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM100</th><th style="border-top: 2px solid #aaa">Choose only 1: File, Field, Record or Field Group Maintenance</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM101</th><th style="border-top: 2px solid #aaa">File is staged for Delete or Initialize </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested an operation on a file that has been staged for deletion or initialization. If you wish to delete or initialize a file, you must first complete this process before invoking another command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM102</th><th style="border-top: 2px solid #aaa">File has already been Created</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM103</th><th style="border-top: 2px solid #aaa">File is staged for Create, Recreate or Initialize </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested an operation on a file that has been staged for creation, recreation, or initialization. If you wish to create, recreate, or initialize a file, you must complete this process first before invoking another command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM104</th><th style="border-top: 2px solid #aaa">File is staged with commands and cannot be deleted</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM105</th><th style="border-top: 2px solid #aaa">There is no existing file by this name </th></tr> | |||
<tr><td /><td><b>Description:</b> You have entered the name of a file that has not been created. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM106</th><th style="border-top: 2px solid #aaa">Field, Record and Field Group name only can be widened</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM107</th><th style="border-top: 2px solid #aaa">File is staged with commands and cannot be recreated </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested the RECREATE option on a file in which commands are staged. Until the staged commands in this file are executed, you cannot recreate the file. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM108</th><th style="border-top: 2px solid #aaa">File must have staged commands to proceed to Commands processing</th></tr> | |||
<tr><td /><td><b>Description:</b> A file needs a staged command, e.g., record DEFINE or file CREATE to proceed to the Execute or Delete Commands screens. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM109</th><th style="border-top: 2px solid #aaa">Increase or Decrease invalid for this file </th></tr> | |||
<tr><td /><td><b>Description:</b> You are requesting an increase or decrease to TABLE B or D for this file and the file does not yet exist; it is still staged for CREATE. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM110</th><th style="border-top: 2px solid #aaa">File is staged with commands and cannot be initialized </th></tr> | |||
<tr><td /><td><b>Description:</b> File Management does not allow you to initialize a file that already has commands staged for it. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM111</th><th style="border-top: 2px solid #aaa">The file is already Secured</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM112</th><th style="border-top: 2px solid #aaa">The file is not Secured - Desecure is invalid</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM113</th><th style="border-top: 2px solid #aaa">Field has already been defined</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM114</th><th style="border-top: 2px solid #aaa">File has no fields or records</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM115</th><th style="border-top: 2px solid #aaa">There is no field to Redefine, Delete, or Rename</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM116</th><th style="border-top: 2px solid #aaa">Field is staged for Delete - cannot Rename or Redefine (or delete)</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM117</th><th style="border-top: 2px solid #aaa">Field is staged for Define - cannot Rename, Redefine, or Delete</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM118</th><th style="border-top: 2px solid #aaa">There is no field by this name</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM119</th><th style="border-top: 2px solid #aaa">Record has already been defined</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM120</th><th style="border-top: 2px solid #aaa">Record has not been defined</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM121</th><th style="border-top: 2px solid #aaa">There is no production record to Redefine, Delete, or Rename</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM122</th><th style="border-top: 2px solid #aaa">Record is staged for Delete - cannot Rename or Redefine</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM123</th><th style="border-top: 2px solid #aaa">There are no valid records to redefine or rename</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM124</th><th style="border-top: 2px solid #aaa">There is no production record by this name</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM125</th><th style="border-top: 2px solid #aaa">There are no valid records to Delete</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM126</th><th style="border-top: 2px solid #aaa">Field Delete has already been requested</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM127</th><th style="border-top: 2px solid #aaa">Record Delete has already been requested</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM128</th><th style="border-top: 2px solid #aaa">There are no valid fields to Delete</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM129</th><th style="border-top: 2px solid #aaa">Field is staged with commands and cannot be Deleted </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested the DELETE option for a field that is staged for either RENAME or REDEFINE. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM130</th> | |||
<th style="border-top: 2px solid #aaa">Record is staged with commands and cannot be Deleted </th></tr><tr><td /><td><b>Description:</b> You requested the DELETE option for a record that is staged for either RENAME or REDEFINE. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM131</th><th style="border-top: 2px solid #aaa">The file is being changed by another user </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested a change to a file that is currently being changed by another user. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM132</th><th style="border-top: 2px solid #aaa">Define is the only valid choice for this file </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested a REDEFINE, DELETE or RENAME option for a new file that has not been created. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM133</th><th style="border-top: 2px solid #aaa">There is no field group to Rename, Delete or Redefine</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM134</th><th style="border-top: 2px solid #aaa">Field group has not been Defined</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM135</th><th style="border-top: 2px solid #aaa">Field group has been Defined </th></tr><tr><td /><td><b>Description:</b> | |||
You are trying to define a field group that already exists. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM136</th><th style="border-top: 2px solid #aaa">The field group is staged for Define - cannot Rename, Redefine, or Delete</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM137</th><th style="border-top: 2px solid #aaa">The field group is staged for Delete - cannot Rename, Redefine, or Delete</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM138</th><th style="border-top: 2px solid #aaa">There are no field groups to Rename, Redefine or Delete</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM139</th><th style="border-top: 2px solid #aaa">A choice is required </th></tr><tr><td /><td><b>Description:</b> | |||
You have not entered a filename or an option after the Field, File, Record or Field Group Maintenance prompts. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM140</th><th style="border-top: 2px solid #aaa">The item to be DOCUMENTed does not exist</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM141</th><th style="border-top: 2px solid #aaa">The file has been staged for SECURE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM142</th><th style="border-top: 2px solid #aaa">The file has been staged for DESECURE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM143</th><th style="border-top: 2px solid #aaa">ERROR: Duplicate file entries - see your Dictionary Administrator </th></tr> | |||
<tr><td /><td><b>Description:</b> More than one dictionary entry was found for the file. Notify your Dictionary Administrator. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM144</th><th style="border-top: 2px solid #aaa">There is no new or existing file by this name</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM145</th><th style="border-top: 2px solid #aaa">A FILENAME is required</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM146</th><th style="border-top: 2px solid #aaa">The file is staged for CREATE - cannot copy (ENTITY)</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM147</th><th style="border-top: 2px solid #aaa">Field groups require that fields be defined to a record</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM148</th><th style="border-top: 2px solid #aaa">Enter a valid option number for the tagged choice</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM149</th><th style="border-top: 2px solid #aaa">Filename must not begin with a number or special character</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM150</th><th style="border-top: 2px solid #aaa">May not copy to an existing file or staged file </th></tr> | |||
<tr><td /><td><b>Description:</b> You have entered the name of a file in after the COPY TO prompt which is the name of a previously created file or the name of a file that is staged for CREATE. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM151</th><th style="border-top: 2px solid #aaa">Choose copy option 1, 2, or 3</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM152</th><th style="border-top: 2px solid #aaa">Enter filename for new file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM153</th><th style="border-top: 2px solid #aaa">There are no fields or records on file to copy</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM154</th><th style="border-top: 2px solid #aaa">There are no fields on file to copy</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM155</th><th style="border-top: 2px solid #aaa">New file is locked to another user - cannot continue copy</th></tr> | |||
<tr><td /><td><b>Description:</b> <p class="note"><b>Note:</b> When an option number is entered in File Management that results in a conflict with SQL/204 DDF, you will receive one of the error messages below, FIM157-FIM160.</p></td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM156</th><th style="border-top: 2px solid #aaa">Reserved word invalid for field names</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM157</th><th style="border-top: 2px solid #aaa">File has been defined to SQLDDF, selection not allowed </th></tr> | |||
<tr><td /><td><b>Description:</b> The File Maintenance selection is not valid for a file that is defined to SQL/204 DDF. The selections not allowed are DELETE, RECREATE, COPY and INITIALIZE. | |||
<p>Enter a number that is valid or perform the operation from SQL/204 DDF.</p> </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM158 </th><th style="border-top: 2px solid #aaa">Field is defined to SQLDDF, field selection not allowed </th></tr> | |||
<tr><td /><td><b>Description:</b> No field maintenance operations are allowed on a field defined to SQL/204 DDF.<p>Perform maintenance on this field through SQL/204 DDF rather than FILEMGMT.</p></td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM159</th><th style="border-top: 2px solid #aaa">File has been defined to SQLDDF, ReCREATE not allowed </th></tr> | |||
<tr><td /><td><b>Description:</b> | |||
You cannot recreate a file defined to SQL/204 DDF. If file was created in SQL/204 DDF, drop the file from SQL/204 DDF and create a new file. If file was mapped from a FILEMGMT file, enter SQL/204 DDF and unmap the file. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM160</th><th style="border-top: 2px solid #aaa">File status incomplete in SQLDDF, file maintenance not allowed </th></tr> | |||
<tr><td /><td><b>Description:</b> The file was incompletely mapped from SQL/204 DDF. | |||
<p>The file status must be resolved through SQL/204 DDF. Enter the SQL/204 DDF and select the mapping option to complete the mapping of this file. If you are unable to map the file, see your system manager.</p></td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM161</th><th style="border-top: 2px solid #aaa">File created in SQLDDF must add fields thru alter in SQLDDF</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM162</th><th style="border-top: 2px solid #aaa">No AVERAGE LENGTH, 20 assumed for field(s)</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM163</th><th style="border-top: 2px solid #aaa">Field Attributes screen is display-only for RENAME/DELETE mode</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM164</th><th style="border-top: 2px solid #aaa">Select fields for RENAME/DELETE from the Field List screen</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM165</th><th style="border-top: 2px solid #aaa">The specified userid has no staged file commands</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM169</th><th style="border-top: 2px solid #aaa">Field is Date time Stamp, fieldname cannot be changed.</th></tr> | |||
<tr><td /><td><b>Description:</b> Datetime Stamp field corresponds to value of DTSFN and cannot be changed.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM170</th><th style="border-top: 2px solid #aaa">WARN: There is no valid Datetime Stamp field defined in file</th></tr> | |||
<tr><td /><td><b>Description:</b> The user is attemping to use a Datetime Stamp feature, but the file does not have the field defined.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM200</th><th style="border-top: 2px solid #aaa">Field|Record name missing </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested the Copy option for a field or record entry but have omitted a new record or field name. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM201</th><th style="border-top: 2px solid #aaa">Missing the 'Copy to' filename </th></tr><tr><td /><td><b>Description:</b> | |||
You have not entered the name of the new file you are creating with the Copy option. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM202</th><th style="border-top: 2px solid #aaa">Field|Record names must be unique when copying to the same file </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested the Copy option for a field or record within a file and have entered the name of a field or record that already exists within that file. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM203</th><th style="border-top: 2px solid #aaa">There are no fields|records on file to copy</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM204</th><th style="border-top: 2px solid #aaa">Field|Record name does not exist</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM205</th><th style="border-top: 2px solid #aaa">Cannot copy all fields|records within the same file </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested the Copy option for all fields or records with in a single file. This option is only valid between files. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM206</th><th style="border-top: 2px solid #aaa">Field|Record name already exists</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM207</th><th style="border-top: 2px solid #aaa">All field|record names are already on 'Copy to' file - cannot copy </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM208</th><th style="border-top: 2px solid #aaa">WARN: Only able to copy nn fields/records to "Copy to" file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM209</th><th style="border-top: 2px solid #aaa">WARN: DISABLE TBO marked as selected with APPLY UPDATES DURING RF</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM250</th><th style="border-top: 2px solid #aaa">Select one of ENTRY, SORTED, HASHED, or UNORDERED options</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM251</th><th style="border-top: 2px solid #aaa">REQ EVRY REC only valid for SORTED or HASHED files </th></tr> | |||
<tr><td /><td><b>Description:</b> You have selected the ENTRY or UNORDERED option as the type of file organization for the file you are creating. You must select the SORT or HASH option. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM252</th><th style="border-top: 2px solid #aaa">SORT/HASH KEY only valid for SORTED or HASHED files </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM253</th><th style="border-top: 2px solid #aaa">Select one of REUSE FIRST or APPEND FIRST options</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM254</th><th style="border-top: 2px solid #aaa">REUSE FIRST option is only valid WITH RDFS </th></tr> | |||
<tr><td /><td><b>Description:</b> You have selected the Reuse First option without selecting the Reuse Record Numbers option; Reuse First is only valid for a file created before Release 9.0 that is organized to reuse record numbers. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM255</th><th style="border-top: 2px solid #aaa">APPEND FIRST option is only valid WITH RDFS </th></tr> | |||
<tr><td /><td><b>Description:</b> You have selected the Reuse First option without selecting the Reuse Record Slots option; Reuse First is only valid for a file that is organized to reuse record slots. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM256</th> | |||
<th style="border-top: 2px solid #aaa">TBO must be disabled if LOCK PENDING UPDATES are disabled </th></tr> | |||
<tr><td /><td><b>Description:</b> You have selected to Disable Lock Pending Updates, but have not chosen to Disable Transaction Backout. You must specify both options. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM257</th><th style="border-top: 2px solid #aaa">Select one of PUBLIC, SEMI-PUBLIC or PRIVATE options</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM258</th><th style="border-top: 2px solid #aaa">SELECT LEVEL must be between 0 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM259</th><th style="border-top: 2px solid #aaa">READ LEVEL must be between 0 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM260</th><th style="border-top: 2px solid #aaa">UPDATE LEVEL must be between 0 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM261</th><th style="border-top: 2px solid #aaa">ADD LEVEL must be between 0 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM262</th><th style="border-top: 2px solid #aaa">KEY FIELD NAME must be specified if RECORD SECURITY chosen</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM263</th><th style="border-top: 2px solid #aaa">KEY FIELD NAME is only valid if RECORD SECURITY chosen</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM264</th> | |||
<th style="border-top: 2px solid #aaa">Make your selection with an 'X'</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM265</th><th style="border-top: 2px solid #aaa">FORMAT FILE must be either Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM266</th><th style="border-top: 2px solid #aaa">VERIFY FILE must be either Y of N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM267</th><th style="border-top: 2px solid #aaa">AVG PROCNAME LEN must be between 1 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM268</th><th style="border-top: 2px solid #aaa">PRCLDEF must be between 0 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM269</th><th style="border-top: 2px solid #aaa">SORT/HASH KEY must be specified </th></tr> | |||
<tr><td /><td><b>Description:</b> You have selected a file organization of either Sorted or Hashed, but have not specified the hash key name. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM270</th><th style="border-top: 2px solid #aaa">If PUBLIC FILE, PRIVDEF must have ADHOC UPDATE privilege set </th></tr> | |||
<tr><td /><td><b>Description:</b> You have selected the Public access option for a file, but have not specified sufficient privileges for the default privilege class so that you can update the file. | |||
<p>If a PUBLIC file, PRIVDEF must have ADHOC UPDATE privileges set.</p></td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM272</th><th style="border-top: 2px solid #aaa">FICREATE is not a supported Model 204 release for this file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM273</th><th style="border-top: 2px solid #aaa">KEY is only valid widen item</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM274</th><th style="border-top: 2px solid #aaa">Expected AVERAGE PAGES PER PROC requires a positive number</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM275</th><th style="border-top: 2px solid #aaa">Expected NUMBER OF PROCEDURES ENTRIES requires a positive number</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM276</th><th style="border-top: 2px solid #aaa">Expected NUMBER OR PROCEDURES has exceeded the DSIZE maximum</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM277</th><th style="border-top: 2px solid #aaa">Expected AVERAGE PAGES PER PROC has exceeded the DSIZE maximum </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM278</th><th style="border-top: 2px solid #aaa">Hash key and Record Security key cannot be the same field </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM279</th><th style="border-top: 2px solid #aaa">Unordered option invalid for files created before 9.0</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM280</th><th style="border-top: 2px solid #aaa">File mode must be INACTIVE for files created before 9.0</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM281</th><th style="border-top: 2px solid #aaa">INACTIVE (I) command mode not available - choose ACTIVE (A)</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM282</th><th style="border-top: 2px solid #aaa">ACTIVE (A) command mode not available - choose INACTIVE (I)</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM283</th><th style="border-top: 2px solid #aaa">WARN: REUSE FIRST marked as selected with RRN for a pre-9.0 file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM284</th><th style="border-top: 2px solid #aaa">RRN not valid for ENTRY ORDER files - choose UNORDERED option</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM285</th><th style="border-top: 2px solid #aaa">'A' or 'I' are the only valid choices</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM286</th><th style="border-top: 2px solid #aaa">WARN: UNORDERED marked as selected with RRN</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM287</th><th style="border-top: 2px solid #aaa">No command mode is valid - contact your Dictionary Administrator</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM288</th><th style="border-top: 2px solid #aaa">INACTIVE command mode is invalid - FICREATE must match current release</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM289</th><th style="border-top: 2px solid #aaa">PDSIZE must not exceed the maximum of 255, will be truncated to 255 </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM290</th><th style="border-top: 2px solid #aaa">FICREATE not supplied, specify item</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM291</th><th style="border-top: 2px solid #aaa">NONE may not be selected with 1NF or NUMERIC VALIDATION.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM292</th><th style="border-top: 2px solid #aaa">TBO may not be disabled with the 1NF FILE MODEL.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM293</th><th style="border-top: 2px solid #aaa">Files cannot be reset to 1NF FILEMODL.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM294</th><th style="border-top: 2px solid #aaa">Files cannot be reset to NUMERIC VALIDATION FILEMODL.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM295</th><th style="border-top: 2px solid #aaa">1NF FILE MODEL requires AT-MOST-ONE field attribute.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM296</th><th style="border-top: 2px solid #aaa">WARN: AT-MOST-ONE makes file inaccessible to pre 2.2 releases.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM297</th><th style="border-top: 2px solid #aaa">WARN: Field level constraint not downward compatible past release 2.1</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM298</th><th style="border-top: 2px solid #aaa">WARN: Redefine to AT-MOST-ONE may fail if field occurrence is gt 1.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM299</th><th style="border-top: 2px solid #aaa">NUMERIC RANGE fields not allowed in 1NF FILE MODEL files.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM300</th><th style="border-top: 2px solid #aaa">Filename cannot begin with 'OUT' 'SYS' 'CCA' or 'TAPE'</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM301</th><th style="border-top: 2px solid #aaa">Filename contains an invalid character</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM302</th><th style="border-top: 2px solid #aaa">NUMERIC RANGE fields not allowed in 1NF FILE MODEL files.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM303</th><th style="border-top: 2px solid #aaa">FRV fields not allowed in 1NF FILE MODEL files.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM304</th><th style="border-top: 2px solid #aaa">AT-MOST-ONE cannot be specified in a Non-TBO file.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM305</th><th style="border-top: 2px solid #aaa">WARN: Turning off TBO with field level constraints defined to file.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM306</th><th style="border-top: 2px solid #aaa">WARN: Multiply occurring fields present in a 1NF file.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM307</th><th style="border-top: 2px solid #aaa">LANGUAGE Option must be US, JAPAN or TURKISH</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM308</th><th style="border-top: 2px solid #aaa">Optimized Field Extract must be an "N" or a "Y"</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM309</th><th style="border-top: 2px solid #aaa">PAGES must be between 1 and 16777216</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM310</th><th style="border-top: 2px solid #aaa">Datetime Stamp parameter (DTSFN) not set in this system</th></tr> | |||
<tr><td /><td><b>Description:</b> In order to use the Datetime Stamp option, the parameter DTSFN must be set in the CCAIN to the fieldname that will be used for Datetime Stamp processing.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM311</th><th style="border-top: 2px solid #aaa">WARN: XAUTOINC will not be set if XSIZE = 0</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM312</th><th style="border-top: 2px solid #aaa">You have selected Datetime stamp, press PF4 to define fields</th></tr> | |||
<tr><td /><td><b>Description:</b> On the Reset screen, the user selected the Datetime stamp option. This message directs the user to now go define the attributes associated with the Datetime stamp field.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM313</th><th style="border-top: 2px solid #aaa">Pages must be between 0 and 16,777,216</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM314</th><th style="border-top: 2px solid #aaa">The maximum value for this field is 16,777,216</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM315</th><th style="border-top: 2px solid #aaa">Use an X to select this field</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM316</th><th style="border-top: 2px solid #aaa">Option only valid with version 6.1 or later file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM317</th><th style="border-top: 2px solid #aaa">This file is already defined as a Datetime Stamp file</th></tr> | |||
<tr><td /><td><b>Description:</b> The user is attempting to define the file as a Datetime Stamp file, but it already is a Datetime Stamp file.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM318</th><th style="border-top: 2px solid #aaa">WARN: must define field for DateTime Stamp</th></tr> | |||
<tr><td /><td><b>Description:</b> The user set FOPT=x'10', indicating a desire to use Datetime Stamp processing, but a field which corresponds to the value of DTSFN has not been defined to the file.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM319</th><th style="border-top: 2px solid #aaa">Enable Datetime Stamp must be an "N" or a "Y"</th></tr> | |||
<tr><td /><td><b>Description:</b> The user entered an invalid character in the Enable Datetime stamp input area.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM320</th><th style="border-top: 2px solid #aaa">Cannot disable Lock Pending Updates with Enable Date Time Stamp</th></tr> | |||
<tr><td /><td><b>Description:</b> The user attempted to select Disable Lock Pending Updates for a Datetime Stamp file.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM321</th><th style="border-top: 2px solid #aaa">Table X pages maximum value is 536,870,911</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM322</th><th style="border-top: 2px solid #aaa">Option only valid with version 6.3 or later file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM323</th><th style="border-top: 2px solid #aaa">Table X Auto Increase not valid with Sorted or Hash</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM324</th><th style="border-top: 2px solid #aaa">Only an X is allowed to select this field</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM325</th><th style="border-top: 2px solid #aaa">This option cannot be selected for a file created prior to version 6</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM351</th><th style="border-top: 2px solid #aaa">Field names are only valid items to document</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM352</th><th style="border-top: 2px solid #aaa">Field names are only valid widened items</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM353</th><th style="border-top: 2px solid #aaa">Incorrect field name syntax</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM354</th><th style="border-top: 2px solid #aaa">Duplicate field name as entered</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM355</th><th style="border-top: 2px solid #aaa">Delete invalid for Sort, Hash, Record Security or DTS field</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM356</th><th style="border-top: 2px solid #aaa">Mark prefix with an 'X' before proceeding to ATTRIBUTES screen</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM400</th><th style="border-top: 2px solid #aaa">KEY must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM401</th><th style="border-top: 2px solid #aaa">INVIS must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM402</th><th style="border-top: 2px solid #aaa">DEFERRABLE must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM403</th><th style="border-top: 2px solid #aaa">NUMERIC RANGE (NR) must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM404</th><th style="border-top: 2px solid #aaa">FRV must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM405</th><th style="border-top: 2px solid #aaa">CODED must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM406</th><th style="border-top: 2px solid #aaa">FEW-VALUED must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM407</th><th style="border-top: 2px solid #aaa">MANY-VALUED must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM408</th><th style="border-top: 2px solid #aaa">NUMBER OF UNIQUE VALUES must be ALL or from 1 to 16,777,216 </th></tr> | |||
<tr><td /><td><b>Description:</b> The field you are defining or redefining is a Key, FRV, Numeric Range, Ordered, or Coded field and requires a value in Number of Unique Values for file sizing of the index space. You can specify ALL to indicate that every record contains a unique occurrence of the field's value. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM409</th><th style="border-top: 2px solid #aaa">NUMBER OF SIGNIFICANT DIGITS must be values 1 to 9</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM410</th><th style="border-top: 2px solid #aaa">STRING must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM411</th><th style="border-top: 2px solid #aaa">BINARY must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM412</th><th style="border-top: 2px solid #aaa">FLOAT must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM413</th><th style="border-top: 2px solid #aaa">LEVEL must be an integer between 0 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM414</th><th style="border-top: 2px solid #aaa">UPDATE AT END must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM415</th><th style="border-top: 2px solid #aaa">PREALLOCATED must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM416</th><th style="border-top: 2px solid #aaa">Length must be a positive integer between 1 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM417</th><th style="border-top: 2px solid #aaa">MIN OCCURS must be an integer greater than zero</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM418</th><th style="border-top: 2px solid #aaa">MAX OCCURS must be an integer greater than zero</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM420</th><th style="border-top: 2px solid #aaa">Preallocated REPEATABLE must be an integer between 1 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM421</th><th style="border-top: 2px solid #aaa">PREALLOCATED PAD must be between 00 and FF</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM422</th><th style="border-top: 2px solid #aaa">PHYSICAL FORMAT must be V or F</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM423</th><th style="border-top: 2px solid #aaa">SIGNIFICANT DIGITS LEADING must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM424</th><th style="border-top: 2px solid #aaa">SIGNIFICANT DIGITS TRAILING must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM425</th><th style="border-top: 2px solid #aaa">MIXED CASE must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM428</th><th style="border-top: 2px solid #aaa">INVISIBLE requires KEY, NUMERIC RANGE, or ORDERED </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM429</th><th style="border-top: 2px solid #aaa">Conflicting attributes: INVISIBLE and attribute</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM430</th><th style="border-top: 2px solid #aaa">Conflicting attributes: HASH and KEY</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM431</th><th style="border-top: 2px solid #aaa">Conflicting attributes: RECORD SECURITY and NON-KEY</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM432</th><th style="border-top: 2px solid #aaa">Conflicting attributes: INVISIBLE and PREALLOCATED</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM442</th><th style="border-top: 2px solid #aaa">Invalid PHYSICAL PICTURE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM445</th><th style="border-top: 2px solid #aaa">MANY-VALUED requires CODED or FRV</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM446</th><th style="border-top: 2px solid #aaa">NUMBER OF UNIQUE VALUES requires KEY, FRV, CODED, ORDERED, or NR</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM454</th><th style="border-top: 2px solid #aaa">FLOAT requires length of 4, 8, or 16</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM455</th><th style="border-top: 2px solid #aaa">Tagged items are WARNINGS. Press ENTER to view messages.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM458</th><th style="border-top: 2px solid #aaa">PREALLOCATED requires a value for LENGTH</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM459</th><th style="border-top: 2px solid #aaa">PREALLOCATED requires a value for REPEATABLE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM461</th><th style="border-top: 2px solid #aaa">Conflicting attributes: PREALLOCATED PAD and NON PREALLOCATED</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM462</th><th style="border-top: 2px solid #aaa">PHYSICAL PICTURE has invalid date format</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM463</th><th style="border-top: 2px solid #aaa">First character of PHYSICAL PICTURE is invalid</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM464</th><th style="border-top: 2px solid #aaa">PHYSICAL PICTURE is missing left parenthesis</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM465</th><th style="border-top: 2px solid #aaa">PHYSICAL PICTURE is missing right parenthesis</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM466</th><th style="border-top: 2px solid #aaa">PHYSICAL PICTURE must have number in parentheses</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM467</th><th style="border-top: 2px solid #aaa">PHYSICAL PICTURE exceeds maximum of setting</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM468</th><th style="border-top: 2px solid #aaa">Conflicting attributes: Variable format and Leading/Trailing 0's</th></tr> | |||
<tr><td /><td><b>Description:</b> <p class="note"><b>Note:</b> The following warning messages (noted by the <b>WARN:</b> prefix) inform you that you have not completed all the information for the field. You can execute the field command, but the sizing algorithm might not be accurate without the information you are missing.</p></td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM469</th><th style="border-top: 2px solid #aaa">WARN: A default length of 6000 will be stored for LOB sizing.</th></tr> | |||
<tr><td /><td><b>Description:</b> On the field attributes screen, when defining a LOB entry, if a length is not added for the field, a default of 6000 will be added.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM470</th><th style="border-top: 2px solid #aaa">WARN: A default length of 20 will be stored for Sizing.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM471</th><th style="border-top: 2px solid #aaa">WARN: MIN OCCURS is null. Used by ACCESS.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM472</th><th style="border-top: 2px solid #aaa">WARN: MAX OCCURS is null. Used by ACCESS.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM473</th><th style="border-top: 2px solid #aaa">WARN: NUMBER OF UNIQUE VALUES is null. "ALL" is assumed.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM474</th><th style="border-top: 2px solid #aaa">WARN: NUMBER OF SIGNIFICANT DIGITS is null. Used by Sizing.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM475</th><th style="border-top: 2px solid #aaa">WARN: PHYSICAL PICTURE is null. Used by ACCESS.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM476</th><th style="border-top: 2px solid #aaa">WARN: PHYSICAL FORMAT is null. Used by ACCESS.</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM479</th><th style="border-top: 2px solid #aaa"> Serious error has occurred. Non-zero return code from SCRLGET </th></tr> | |||
<tr><td /><td><b>Description:</b> There is incorrect information in the scrolling records in the M204TEMP record which has been passed from the Field List to the Field Attributes process. Notify Technical Support. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM480</th><th style="border-top: 2px solid #aaa">WARN: Preallocated field invalid if data exists in the file </th></tr> | |||
<tr><td /><td><b>Description:</b> You are defining a field as Preallocated to a file that already has been created. This is illegal in Model 204. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM481</th><th style="border-top: 2px solid #aaa">MIN OCCURS is larger than MAX OCCURS</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM482</th><th style="border-top: 2px solid #aaa">FLOAT is invalid for a file created earlier than 8.0 </th></tr> | |||
<tr><td /><td><b>Description:</b> FLOAT is not a valid data type for files created with a version of Model 204 that is earlier than 8.0. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM483</th><th style="border-top: 2px solid #aaa">File created on 7.1 version is not transformed for FLOAT </th></tr> | |||
<tr><td /><td><b>Description:</b> You are trying to define a field with the FLOAT data type. However, the file was created with Model 204 release 7.1 and is not transformed for this data type. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM484</th><th style="border-top: 2px solid #aaa">Conflicting attributes: INVISIBLE and LENGTH</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM485</th><th style="border-top: 2px solid #aaa">Only VISIBLE fields can be renamed </th></tr> | |||
<tr><td /><td><b>Description:</b> You have requested to rename a field that is defined as invisible. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM493</th><th style="border-top: 2px solid #aaa">Conflicting attributes: HASH or SORT and not STRING</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM494</th><th style="border-top: 2px solid #aaa">HASH/SORT key cannot be PREALLOCATED if not req'd in every rcd</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM495</th><th style="border-top: 2px solid #aaa">WARN: RECORD SECURITY key average length is less than 10</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM496</th><th style="border-top: 2px solid #aaa">HASH/SORT key cannot be multiply occurring</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM497</th><th style="border-top: 2px solid #aaa">WARN: Invalid PICTURE for NUMERIC RANGE - used by ACCESS</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM498</th><th style="border-top: 2px solid #aaa">ORDERED must be Y or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM499</th><th style="border-top: 2px solid #aaa">TREETYPE must be C or N</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM500</th><th style="border-top: 2px solid #aaa">LRESERVE must be an integer between 0 and 99 inclusive</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM501</th><th style="border-top: 2px solid #aaa">NRESERVE must be an integer between 0 and 99 inclusive</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM502</th><th style="border-top: 2px solid #aaa">SPLITPCT must be an integer between 1 and 100 inclusive</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM503</th><th style="border-top: 2px solid #aaa">IMMED must be an integer between 0 and 255 inclusive</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM504</th><th style="border-top: 2px solid #aaa">WARN: Tagged item is null. Used by Sizing</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM505</th><th style="border-top: 2px solid #aaa">Second page of attributes applies only to ORDERED fields</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM508</th><th style="border-top: 2px solid #aaa">SIZING PARAMETER must be an integer between 0 and 100 inclusive</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM509</th><th style="border-top: 2px solid #aaa">ORDERED invalid for file created earlier than 9.0</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM510</th><th style="border-top: 2px solid #aaa">UNIQUE must be yes or no</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM511</th><th style="border-top: 2px solid #aaa">UNIQUE cannot be specified with DEFERRABLE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM512</th><th style="border-top: 2px solid #aaa">WARN: Redefine to UNIQUE will fail if non-unique values present</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM513</th><th style="border-top: 2px solid #aaa">UNIQUE cannot be specified for Non-TBO file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM514</th><th style="border-top: 2px solid #aaa">Datetime Stamp field cannot be UNIQUE.</th></tr> | |||
<tr><td /><td><b>Description:</b> On the field attributes screen, when defining a Datetime Stamp field, the attribute UNIQUE is not allowed.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM515</th><th style="border-top: 2px solid #aaa">DATETIME STAMP field cannot be a BLOB or CLOB.</th></tr> | |||
<tr><td /><td><b>Description:</b> On the field attributes screen, when defining a Datetime Stamp field, the attributes BLOB and CLOB are not allowed.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM550</th><th style="border-top: 2px solid #aaa">Record names are only valid items to document</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM551</th><th style="border-top: 2px solid #aaa">Record names are only valid widened items</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM552</th><th style="border-top: 2px solid #aaa">Incorrect record name syntax </th></tr> | |||
<tr><td /><td><b>Description:</b> You have entered a record name that does not meet the naming conventions for dictionary entries. It contains invalid characters or characters that are illegal as field names in a User Language programs. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM553</th><th style="border-top: 2px solid #aaa">Duplicate record name as entered</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM555</th><th style="border-top: 2px solid #aaa">Incorrect EXPECTED INCREASE Percentage</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM556</th><th style="border-top: 2px solid #aaa">EXPECTED INCREASE percentage must be numeric</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM557</th><th style="border-top: 2px solid #aaa">NUMBER OF RECORDS must be numeric and greater than zero</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM558</th><th style="border-top: 2px solid #aaa">Incorrect NUMBER OF RECORDS entered</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM559</th><th style="border-top: 2px solid #aaa">NUMBER OF RECORDS exceeds allowable maximum for the file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM560</th><th style="border-top: 2px solid #aaa">Mark prefix with an 'X' before proceeding to Record Definition </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM601</th><th style="border-top: 2px solid #aaa">Recordname, Fieldname, Rectype Id Value are only valid widened items </th></tr> | |||
<tr><td /><td><b>Description:</b> You issued the WIDen command without placing the cursor on a record name, field name or Rectype Id Value. Place the cursor on the name and reissue the command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM602</th><th style="border-top: 2px solid #aaa">% Field Occur must be numeric </th></tr> | |||
<tr><td /><td><b>Description:</b> You entered a non-numeric value in Percent Field Occurrence for a field. Re-enter the value. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM603</th><th style="border-top: 2px solid #aaa">Unique id must be X or D if it has previously been selected </th></tr> | |||
<tr><td /><td><b>Description:</b> The field you are working with has already been specified as a unique identifier for the record. If you do not want the field as a unique identifier, replace the X under the Unique Id prompt with a D. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM604</th><th style="border-top: 2px solid #aaa">Unique id must be X, '_' or EOF </th></tr> | |||
<tr><td /><td><b>Description:</b> The field you are working with has not been specified as a unique identifier for the record. If you want to specify the field as a unique identifier, you must enter X under the prompt; otherwise, delete the character you entered. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM605</th><th style="border-top: 2px solid #aaa">Rectype id must be X or D if it has previously been selected </th></tr> | |||
<tr><td /><td><b>Description:</b> The field you are working with has already been specified as a rectype id field for the record. If you do not want the field to be a rectype id field, type an X over the D. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM606</th><th style="border-top: 2px solid #aaa">Rectype id must be X, '_' or EOF </th></tr> | |||
<tr><td /><td><b>Description:</b> The field you are working was not specified as a rectype id field for the record. If you want to define the field as a rectype id field, type an X below the Rectype Id prompt. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM607</th><th style="border-top: 2px solid #aaa">Prefix for selected fields must be X, D, '_' or ' ' </th></tr> | |||
<tr><td /><td><b>Description:</b> Enter a D to remove the field from the record you are working on. Enter an X to modify the characteristics of the field. If you do not want to modify or delete it, blank out the invalid character. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM608</th><th style="border-top: 2px solid #aaa">Prefix for unselected fields must be X</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM610</th><th style="border-top: 2px solid #aaa">Invalid rectype id data value </th></tr> | |||
<tr><td /><td><b>Description:</b> The rectype id value you entered was not valid. Reenter the value. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM611</th><th style="border-top: 2px solid #aaa">No records have been selected for display</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM612</th><th style="border-top: 2px solid #aaa">Rectype id data value cannot be blank if Rectype id selected </th></tr> | |||
<tr><td /><td><b>Description:</b> You selected a field to be a rectype id field for the record. Enter the corresponding rectype id data value. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM613</th><th style="border-top: 2px solid #aaa">Enter an X to select Rectype id </th></tr> | |||
<tr><td /><td><b>Description:</b> You entered a rectype id data value without entering an X under the rectype id data value prompt. Enter an X to specify it as a rectype id field, otherwise the data value will be ignored. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM614</th><th style="border-top: 2px solid #aaa">Field must be deleted from Fld Grp before it is deleted from Record </th></tr> | |||
<tr><td /><td><b>Description:</b> This field is part of a field group in this record. File management will not automatically delete the field from the field group. You must go to the field group definition/redefinition and remove the field from its field group. Return to record definition/redefinition to remove the field from the record. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM615</th><th style="border-top: 2px solid #aaa">Preallocated fields cannot be deleted from the record definitions list </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM616</th><th style="border-top: 2px solid #aaa">Sort/Hash key required in every record cannot be deleted</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM617</th><th style="border-top: 2px solid #aaa">Preallocated fields must be present on 100 percent of records</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM618</th><th style="border-top: 2px solid #aaa">Date Time Stamp cannot be deleted from record</th></tr> | |||
<tr><td /><td><b>Description:</b> On the record definition screen, when attempting to delete a Datetime Stamp field from a record, the field cannot be deleted.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM619</th><th style="border-top: 2px solid #aaa">Prefix for unselected fields must be X, "_" OR " "</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM650</th><th style="border-top: 2px solid #aaa">Cursor is not on an input item</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM651</th><th style="border-top: 2px solid #aaa">Record and Field Group names are only valid documented items </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM652</th><th style="border-top: 2px solid #aaa">Incorrect Field Group name syntax</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM653</th><th style="border-top: 2px solid #aaa">Duplicate Field Group name as entered</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM654</th><th style="border-top: 2px solid #aaa">Field group must be saved before it is documented</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM655</th><th style="border-top: 2px solid #aaa">Mark Record prefix with an X before proceeding to FldGrp Defn</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM656</th><th style="border-top: 2px solid #aaa">You have not marked or entered any new field groups to define</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM657</th><th style="border-top: 2px solid #aaa">Mark a FldGrp prefix with an X before proceeding to FldGrp Defn</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM658</th><th style="border-top: 2px solid #aaa">You must mark field groups and records to enter FldGrp Defn</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM659</th><th style="border-top: 2px solid #aaa">There are no field groups marked</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM660</th><th style="border-top: 2px solid #aaa">Field groups require that fields be defined to a record</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM661</th><th style="border-top: 2px solid #aaa">WARN: Field groups will not be saved unless you mark a prefix</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM662</th><th style="border-top: 2px solid #aaa">WARN: You must proceed to FldGrp Definition to save any changes</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM663</th><th style="border-top: 2px solid #aaa">You have marked more records than field groups to define </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM664</th><th style="border-top: 2px solid #aaa">Record and Field Group names are only valid widened items</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM675</th><th style="border-top: 2px solid #aaa">Record name, Fld Grp name, Field name are only valid widened items </th></tr> | |||
<tr><td /><td><b>Description:</b> You have issued the WIDen command without placing the cursor on a record name, field group name, or field name. Place the cursor on the desired name and reissue the command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM676</th><th style="border-top: 2px solid #aaa">Select a Field Group by marking it with an X </th></tr> | |||
<tr><td /><td><b>Description:</b> You have entered the SWItch command without selecting another field group to define or redefine. Place an X in the prefix area next to the field group you want to work on and reenter the command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM677</th><th style="border-top: 2px solid #aaa">WARN: Avg Occurs value for all fields in the group do not match </th></tr> | |||
<tr><td /><td><b>Description:</b> File Management expects the average number of occurrences for each field in a field group to be the same. You may define field groups whose fields have different average occurs values; however, you will receive this warning message. You can ignore the message if you want to proceed defining or redefining field groups. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM678</th><th style="border-top: 2px solid #aaa">Prefix for selected fields must be D </th></tr> | |||
<tr><td /><td><b>Description:</b> You have entered an invalid character in the prefix area or a field in a field group. Enter a D to remove the field from the field group or blank out the invalid character. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM679</th><th style="border-top: 2px solid #aaa">Prefix for field groups must be X </th></tr> | |||
<tr><td /><td><b>Description:</b> You have entered an invalid character in the prefix area of a field group name. Enter an X to define or redefine a field group or blank out the invalid character. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM680</th><th style="border-top: 2px solid #aaa">Select a field group and SWItch before selecting fields </th></tr> | |||
<tr><td /><td><b>Description:</b> You have attempted to select fields for a field group but you have not selected a field group. Delete the X's you have filled in, return to the "Remaining Field Groups" section, select a field group and enter the SWItch command (PF9). Return to the "Remaining Fields in Record" section and select the fields in this field group. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM681</th><th style="border-top: 2px solid #aaa">WARN: ACCESS cannot use singly occurring fields </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM725</th><th style="border-top: 2px solid #aaa">Transaction Backout file may not disable LPUs </th></tr> | |||
<tr><td /><td><b>Description:</b> You are requesting the Disable Lock Pending Update option for a file which is specified to run with Transaction Backout.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM726</th><th style="border-top: 2px solid #aaa">BRESERVE cannot be larger than (PAGESIZE - 40)</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM727</th><th style="border-top: 2px solid #aaa">DRESERVE must be between 1 and 100</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM728</th><th style="border-top: 2px solid #aaa">Can only select RECORD SECURITY during CREATE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM800</th><th style="border-top: 2px solid #aaa">BSIZE is non-numeric, negative or exceeds allowable maximum</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM801</th><th style="border-top: 2px solid #aaa">BSIZE EXCEEDS ALLOWABLE MAXIMUM - FILE REUSES RECORD SLOTS</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM802</th><th style="border-top: 2px solid #aaa">New BSIZE cannot be less than the number of TABLEB pages used </th></tr> | |||
<tr><td /><td><b>Description:</b> You cannot decrease Table B to a value less than the number of pages used in the file (BHIGHPG). </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM803</th><th style="border-top: 2px solid #aaa">DSIZE is non-numeric, negative or exceeds allowable maximum</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM804</th><th style="border-top: 2px solid #aaa">New DSIZE cannot be less than the number of TABLED pages used </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM805</th><th style="border-top: 2px solid #aaa">Dataset information is incomplete </th></tr> | |||
<tr><td /><td><b>Description:</b> When you are adding new data sets to a file, you must supply the DD name, data set name, device type, and trk/blks. These are used by sizing and as part of the CREATE and INCREASE commands. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM806</th><th style="border-top: 2px solid #aaa">DDname cannot begin with OUT SYS CCA or TAPE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM807</th><th style="border-top: 2px solid #aaa">Duplicate DDnames not allowed</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM808</th><th style="border-top: 2px solid #aaa">Dataset name contains an invalid character</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM809</th><th style="border-top: 2px solid #aaa">Dataset name is missing a parenthesis</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM810</th><th style="border-top: 2px solid #aaa">Duplicate Dataset names not allowed</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM811</th><th style="border-top: 2px solid #aaa">Invalid device type</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM812</th><th style="border-top: 2px solid #aaa">Track or block allocation is not numeric</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM813</th><th style="border-top: 2px solid #aaa">Total table sizes too large for file </th></tr> | |||
<tr><td /><td><b>Description:</b> You requested to INCREASE a file and the addition of all new table sizes exceeded the allocated pages for the current file (including FREESIZE). </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM814</th><th style="border-top: 2px solid #aaa">Password required</th></tr> | |||
<tr><td /><td><b>Description:</b> The file you are requesting to INCREASE or DECREASE requires a read-only password. The password is needed so you can VIEW the file's BHIGHPG and DPGSUSED parameter values. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM815</th><th style="border-top: 2px solid #aaa">Insufficient FREESIZE for Table B increase</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM816</th><th style="border-top: 2px solid #aaa">Insufficient FREESIZE for Table D increase</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM817</th><th style="border-top: 2px solid #aaa">DDname contains an invalid character</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM818</th><th style="border-top: 2px solid #aaa">DDname is the name of a file or staged file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM819</th><th style="border-top: 2px solid #aaa">DDname cannot begin with a number</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM820</th><th style="border-top: 2px solid #aaa">BSIZE must be an integer between 1 and 16777216</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM821</th><th style="border-top: 2px solid #aaa">DSIZE must be an integer between 1 and 16777216</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM822</th><th style="border-top: 2px solid #aaa">Insufficient FREESIZE for Table E increase</th></tr> | |||
<tr><td /><td><b>Description:</b> On the sizing screen, an increase in ESIZE must be less than or equal to what is available in FREESIZE.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM823 </th><th style="border-top: 2px solid #aaa">Table E decrease cannot be less than 20</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM824 </th><th style="border-top: 2px solid #aaa">Table X cannot be decreased to 0</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM825 </th><th style="border-top: 2px solid #aaa">Table X cannot exceed 536870911</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM826 </th><th style="border-top: 2px solid #aaa">Table X cannot be decreased to 0 without recreate</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM827 </th><th style="border-top: 2px solid #aaa">ESIZE is non-numeric, negative or exceeds allowable maximum</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM828 </th><th style="border-top: 2px solid #aaa">You are not authorized to view file parameters</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM829 </th><th style="border-top: 2px solid #aaa">New ESIZE cannot be less than the number of TABLEE pages used</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM830 </th><th style="border-top: 2px solid #aaa">No NUMBER UNIQUE VALUES, 1 per record assumed for field(s)</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM831 </th><th style="border-top: 2px solid #aaa">Calculated Esize too large - maximum assumed</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM832 </th><th style="border-top: 2px solid #aaa">XSIZE can only be used with entry order and unordered files</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM833 </th><th style="border-top: 2px solid #aaa">XSIZE cannot be zero if XAUTOINC is set</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM834 </th><th style="border-top: 2px solid #aaa">BSIZE must be an integer between 1 and 98304</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM850</th><th style="border-top: 2px solid #aaa">BRESERVE too large for table B page </th></tr> | |||
<tr><td /><td><b>Description:</b> BRESERVE must be no longer than (PAGESZ-40). </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM851</th><th style="border-top: 2px solid #aaa">DRESERVE must be between 0 and 100</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM852</th><th style="border-top: 2px solid #aaa">Page size must be 6184, 7208, 3624, or 3368</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM853</th><th style="border-top: 2px solid #aaa">FVFPG parameter must be between 1 and 65,536</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM854</th><th style="border-top: 2px solid #aaa">MVFPG parameter must be between 1 and 65,536</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM855</th><th style="border-top: 2px solid #aaa">BRECPPG * BSIZE must not exceed 16,777,216</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM856</th><th style="border-top: 2px solid #aaa">CSIZE must be an integer between 1 and 65,536</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM857</th><th style="border-top: 2px solid #aaa">ASIZE must be between 1 and 196,605</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM858</th><th style="border-top: 2px solid #aaa">BEXTOVFL pages in error </th></tr> | |||
<tr><td /><td><b>Description:</b> You are creating a sorted file and the values of the stored index (BEXTOVFL) extra overflow pages (BPGPOVFL), master overflow pages and (BPGPMSTR) master sort pages are not specified correctly. Refer to the chapter on sorted files in the Rocket Model 204 documentation wiki "Model 204 files" pages. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM859</th><th style="border-top: 2px solid #aaa">BPGPOVFL pages in error</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM860</th><th style="border-top: 2px solid #aaa">BPGPMSTR pages in error</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM861</th><th style="border-top: 2px solid #aaa">Sorted files are required to have master and overflow pages </th></tr> | |||
<tr><td /><td><b>Description:</b> You are working with a sorted file and have not completed the BEXTOUFL, BPGPOVFL and BPGPMSTR parameters. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM862</th><th style="border-top: 2px solid #aaa">ATRPG * ASTRPPG exceeds 4000</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM863</th><th style="border-top: 2px solid #aaa">ATRPG, FVFPG, and MVFPG do not equal ASIZE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM864</th><th style="border-top: 2px solid #aaa">PDSIZE and PDSTRPPG required if using procedures </th></tr> | |||
<tr><td /><td><b>Description:</b> You have specified that the file you working on will contain procedures (EXPECTED PROCS) or there are procedures entries linked to it in the dictionary, and the parameters used to size the procedure dictionary (PDSIZE/PDSTRPPG) are null. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM865</th><th style="border-top: 2px solid #aaa">FREESIZE parameter in error</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM866</th><th style="border-top: 2px solid #aaa">WARN: Total number of records is 0, default table sizes used </th></tr> | |||
<tr><td /><td><b>Description:</b> When calculating the file sizes, the system did not find any records linked to the file you are working on or found no value in the Total Number of Records on the file entry. The file was sized using the default table sizes in Model 204. See the parameter descriptions for ASIZE, BSIZE, CSIZE, and DSIZE for the default sizes. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM867</th><th style="border-top: 2px solid #aaa">ASTRPPG must be numeric, between 1 and 4,000</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM868</th><th style="border-top: 2px solid #aaa">Calculated Dsize too large - maximum assumed </th></tr> | |||
<tr><td /><td><b>Description:</b> In calculating DSIZE during sizing, you exceeded the maximum value for DSIZE, so sizing used the maximum value. See the parameter description of DSIZE for details. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM869</th><th style="border-top: 2px solid #aaa">ATRPG must be numeric, between 1 and 4,000</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM870</th><th style="border-top: 2px solid #aaa">PDSIZE must be numeric, between 1 and 255</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM871</th><th style="border-top: 2px solid #aaa">PDSTRPPG must be numeric, between 1 and 256</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM872</th><th style="border-top: 2px solid #aaa">BRESERVE must be numeric and less than PAGESZ - 40</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM873</th><th style="border-top: 2px solid #aaa">Calculated Csize too large - max assumed </th></tr> | |||
<tr><td /><td><b>Description:</b> When you were sizing the file, the CSIZE size you calculated exceeded the Model 204 maximum, the maximum value was used. See the CSIZE parameter description for details.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM874</th><th style="border-top: 2px solid #aaa">WARN: tracks not recalculated -- old value not changed </th></tr> | |||
<tr><td /><td><b>Description:</b> File Management calculates disk requirements only if there is one data set per file. If there are more than one data sets per file, you must enter the track or block allocation next to the corresponding device and data set name. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM875</th><th style="border-top: 2px solid #aaa">BRECPPG must be an integer value between 1 and 9999</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM876</th><th style="border-top: 2px solid #aaa">PDSIZE has changed, you may want to ReCREATE the file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM877</th><th style="border-top: 2px solid #aaa">ASIZE has changed, you may want to ReCREATE the file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM878</th><th style="border-top: 2px solid #aaa">Press ENTER to view multiple messages</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM879</th><th style="border-top: 2px solid #aaa">BSIZE increase is larger than HASHED table limit</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM880</th><th style="border-top: 2px solid #aaa">CSIZE has changed, you may want to ReCREATE the file</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM881</th><th style="border-top: 2px solid #aaa">Maximum number of preallocated fields is exceeded</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM882</th><th style="border-top: 2px solid #aaa">Default values assumed for blank screen items </th></tr> | |||
<tr><td /><td><b>Description:</b> You have chosen to redisplay a screen and all the null items on it were replaced with their default values. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM883</th><th style="border-top: 2px solid #aaa">FREESIZE recalculated for new table sizes</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM884</th><th style="border-top: 2px solid #aaa">BREUSE must be between 1 and 100</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM885</th><th style="border-top: 2px solid #aaa">DPGSRES WITH %NUMTXT WITH 0 and 32767</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM887</th><th style="border-top: 2px solid #aaa">DPGSRES must be between 0 and 32767, and no larger than DSIZE</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM900</th><th style="border-top: 2px solid #aaa">DSIZE must be an integer value between 1 and 65536</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM901</th><th style="border-top: 2px solid #aaa">USE file is needed for a report </th></tr> | |||
<tr><td /><td><b>Description:</b> You must specify a USE (directed output) name at the USE prompt on the screen. Type in the appropriate USE name and re-execute the command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM902</th><th style="border-top: 2px solid #aaa">Active or Inactive modes must be selected for command execution </th></tr> | |||
<tr><td /><td><b>Description:</b> You must select Active or Inactive mode for the command you wish to execute. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM903</th><th style="border-top: 2px solid #aaa">USE file is not defined, nothing printed </th></tr> | |||
<tr><td /><td><b>Description:</b> The USE (directed output) name that you specified is not defined. Check to make sure the name of the file is spelled correctly. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM904</th><th style="border-top: 2px solid #aaa">The only valid prefix value is X(select) | D(delete) </th></tr> | |||
<tr><td /><td><b>Description:</b> You have typed something other than X or D on screen where only X (execute) or D (delete) are valid. Check the prefix areas of all lines and try again. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM905</th><th style="border-top: 2px solid #aaa">Item definition must be complete before selecting a command </th></tr> | |||
<tr><td /><td><b>Description:</b> You selected a command that cannot be executed until you finish defining an item. Transfer to the appropriate File Management screen to complete the definition.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM906</th><th style="border-top: 2px solid #aaa">Choose only procedure or USE output for commands </th></tr> | |||
<tr><td /><td><b>Description:</b> You have chosen both procedure and USE output on a screen where only one of these options is valid. Correct the screen and try again. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM907</th><th style="border-top: 2px solid #aaa">Unable to open procedure file to store commands (for IN option) </th></tr> | |||
<tr><td /><td><b>Description:</b> The procedure file you specified cannot be opened. Check the file name and password. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM908</th><th style="border-top: 2px solid #aaa">Unable to store commands in procedure file (for IN option) </th></tr> | |||
<tr><td /><td><b>Description:</b> The privileges specified for the procedure file you are using do not allow you to define any new procedures. Check the file name and password. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM909</th><th style="border-top: 2px solid #aaa">ON ATTN was hit, use Pf3 to QUIt </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM910</th><th style="border-top: 2px solid #aaa">error-dependent message </th></tr> | |||
<tr><td /><td><b>Description:</b> File Management encountered a Model 204 error. You can find the Model 204 error explanation elsewhere in this manual. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM911</th><th style="border-top: 2px solid #aaa">Unresolved enqueue conflict, reenter command or quit</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM912</th><th style="border-top: 2px solid #aaa">Choose only 1 mode for execution of commands </th></tr> | |||
<tr><td /><td><b>Description:</b> You are on a screen which permits only ACTIVE or INACTIVE mode. Check to make sure you have requested only one of these commands. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM913</th><th style="border-top: 2px solid #aaa">Scroll amount must be a positive integer </th></tr> | |||
<tr><td /><td><b>Description:</b> You must use a null (for a full screen) or a positive integer in a scroll command argument. Check the numbers and try again. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM914</th><th style="border-top: 2px solid #aaa">No space available in file to store the procedure </th></tr> | |||
<tr><td /><td><b>Description:</b> There is insufficient space in TABLE D of the specified file to store the procedure with commands. Either choose a different file name or free space in the specified file by deleting procedures in the file. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM915</th><th style="border-top: 2px solid #aaa">FILEMGMT subsystem files are invalid for storing procedures </th></tr> | |||
<tr><td /><td><b>Description:</b> Files used for storing command procedures in inactive mode cannot be chosen from among files used by the FILEMGMT subsystem. These files include: METADATA, DATALINK, M204PROC, and M204TEMP. Change the name of the procedure file and try again. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM916</th><th style="border-top: 2px solid #aaa">Use DICTADMIN facility to define File Management execution options </th></tr> | |||
<tr><td /><td><b>Description:</b> The Dictionary Administration facility enables you to define execution options for &fm. commands. If no options are defined as valid, no commands can be executed. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM917</th><th style="border-top: 2px solid #aaa">USE name may not begin with 'SYS', 'CCA', or 'TAPE'</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM918</th><th style="border-top: 2px solid #aaa">Procfile name may not begin with 'OUT', 'SYS', or 'CCA' </th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM930</th><th style="border-top: 2px solid #aaa">Report printed </th></tr> | |||
<tr><td /><td><b>Description:</b> This is an informational message indicating that a print command has been executed. Check the STATUS field for the command to determine whether the dictionary has been updated. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM931</th><th style="border-top: 2px solid #aaa">Selected commands deleted </th></tr> | |||
<tr><td /><td><b>Description:</b> This is an informational message indicating that the commands you selected have been deleted. Check the STATUS command to determine whether the dictionary has been updated. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM932</th><th style="border-top: 2px solid #aaa">Selected commands executed successfully </th></tr> | |||
<tr><td /><td><b>Description:</b> The commands selected have been executed without errors. All command statuses should be "successful." This message appears only in Active Immediate mode. The dictionary has been updated to reflect the changes for each successful command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM933</th><th style="border-top: 2px solid #aaa">Selected commands pending </th></tr> | |||
<tr><td /><td><b>Description:</b> The commands selected have been marked as pending for active execution in batch mode. The dictionary has not been updated to reflect the changes. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM934</th><th style="border-top: 2px solid #aaa">Selected commands generated </th></tr> | |||
<tr><td /><td><b>Description:</b> The commands selected have been generated through dictionary output or to a procedure. The dictionary has not been updated to reflect the changes. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM935</th><th style="border-top: 2px solid #aaa">No commands selected </th></tr> | |||
<tr><td /><td><b>Description:</b> You entered the EXEcute/DELete command but did not select any commands for execution or deletion. Insert an X (for EXEcute) or a D (for DELete) to select each command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM936</th><th style="border-top: 2px solid #aaa">Selected commands executed, check command statuses for errors </th></tr> | |||
<tr><td /><td><b>Description:</b> The commands selected have been executed, but some or all of the commands might have errors. Check the STATUS field for each command to determine whether the command was successful or not. The dictionary has been updated to reflect the changes for only the successful command. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM937 </th><th style="border-top: 2px solid #aaa">Warning: Subsystem(s) use file ! PF3=Quit, PF6/12=Process</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM940</th><th style="border-top: 2px solid #aaa">M204 command: text of Model 204 command </th></tr> | |||
<tr><td /><td><b>Description:</b> This is an informational message that appears in the audit trail only. It is generated for each Model 204 command generated by the File Management facility. </td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM941</th><th style="border-top: 2px solid #aaa">Blinking fld is AVG LEN <br /> | |||
MULTIPLIER H=Hundreds,T=Thousands, M=Millions</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM942</th><th style="border-top: 2px solid #aaa">Warn: ESIZE must be greater than 20.</th></tr> | |||
<tr><td /><td><b>Description:</b> The minimum size for a BLOB is > 20.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM943</th><th style="border-top: 2px solid #aaa">Avg Length must be between 1 and 9999</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM944</th><th style="border-top: 2px solid #aaa">Datetime Stamp field cannot be INVISIBLE</th></tr> | |||
<tr><td /><td><b>Description:</b> On the field attributes screen, when defining a Datetime Stamp field, the attribute INVISIBLE is not allowed.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM945</th><th style="border-top: 2px solid #aaa">XSIZE can only be used with entry order and unordered files</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM946</th><th style="border-top: 2px solid #aaa">Date Time Stamp cannot be multiply occurring</th></tr> | |||
<tr><td /><td><b>Description:</b> On the field attributes screen, when defining a Date Time Stamp field, the attribute OCCURS must be one.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM947</th><th style="border-top: 2px solid #aaa">Only values of 0 or 1 are valid for RECRDOPT</th></tr> | |||
<tr><td /><td><b>Description:</b> On the sizing screen, only values of 0 or 1 are valid for RECRDOPT.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM948</th><th style="border-top: 2px solid #aaa">XSIZE value is outside range of allowed values 0 to 536870911</th></tr> | |||
<tr><td /><td><b>Description:</b> On the sizing screen, XSIZE must be between 0 and 536870911.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM949</th><th style="border-top: 2px solid #aaa">File must be recreated to change XSIZE</th></tr> | |||
<tr><td /><td><b>Description:</b> On the sizing screen, when updating sizing information, if you now want to use TableX, the file must be recreated.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM950</th><th style="border-top: 2px solid #aaa">XRESERVE, XRECPPG and RECRDOPT not valid without XSIZE</th></tr> | |||
<tr><td /><td><b>Description:</b> On the sizing screen, XSIZE must have a non-zero value before setting XRESERVE, XRECPPG or RECRDOPT.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM951</th><th style="border-top: 2px solid #aaa">XRESERVE, XRECPPG must be > 0 when XSIZE is > 0</th></tr> | |||
<tr><td /><td><b>Description:</b> If XSIZE is a positive non-zero number, then XRESERVE and XRECPPG must also be positive, non-zero numbers.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM952</th><th style="border-top: 2px solid #aaa">Insufficient FREESIZE for TABLEX increase</th></tr> | |||
<tr><td /><td><b>Description:</b> When attempting to increase the size of Table X, there must be sufficient pages available in FREESIZE to handle the increase.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM953</th><th style="border-top: 2px solid #aaa">XRESERVE valid values from 0 to 6140</th></tr> | |||
<tr><td /><td><b>Description:</b> On the sizing screen, XRESERVE must be between 0 and 6140.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM954 </th><th style="border-top: 2px solid #aaa">Trks/Blks not filled in -- Use PF9 to size</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM955</th><th style="border-top: 2px solid #aaa">XSIZE cannot be zero if AUTOINC is set</th></tr> | |||
<tr><td /><td><b>Description:</b> On the File Definition - Organization screen, a non-zero value was entered for "Table X Auto Increase Pages". Revisit that screen and reset that value to zero before attempting to change XSIZE to zero on the sizing screen.</td></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM956</th><th style="border-top: 2px solid #aaa">ESIZE must be an integer value between 1 and 1073741823</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM957</th><th style="border-top: 2px solid #aaa">Insufficient FREESIZE for table E increase</th></tr> | |||
<tr class="head"><th style="border-top: 2px solid #aaa">FIM999</th><th style="border-top: 2px solid #aaa">The Documentation Facility has not been started</th></tr> | |||
</table> | |||
==SUBSYSMGMT error messages== | ==SUBSYSMGMT error messages== | ||
Line 1,089: | Line 2,131: | ||
Then resubmit the job. If the error reappears, contact Technical Support and report the TYPE code.</td></tr> | Then resubmit the job. If the error reappears, contact Technical Support and report the TYPE code.</td></tr> | ||
</table> | </table> | ||
[[Category: Dictionary/204]] |
Latest revision as of 22:44, 17 March 2017
Number | Message text |
---|---|
SHR000 | Access to <subsystem name> facility is not authorized |
Description: You are not authorized to use the facility you selected. Contact the administrator for that facility. | |
SHR001 | A facility may not invoke itself |
Description: You have attempted to invoke the facility you are currently using. Correct the facility name. | |
SHR002 | The <facility name> facility is not defined |
Description: You have attempted to invoke a facility that is not defined or is not installed. | |
SHR003 | The <facility name> facility is not currently active |
Description: You have tried to invoke a subsystem that has not yet been started. Check the facility name. If you typed it correctly, contact the facility administrator to start the facility. | |
SHR004 | The <facility name> facility requires system managers privilege |
SHR005 | Invoked facility <facility name> is no longer active |
Description: The facility you invoked has been stopped. Contact the facility administrator to start the facility. | |
SHR006 | Invoking facility <facility name> is no longer active |
Description: The facility you should have returned to after invoking another facility has been stopped. Contact the facility administrator to start the facility. | |
SHR010 | Enter a valid command or PF key |
Description: You have made an error typing a command or have pressed a PF key that does not exist for the particular screen you are on.
Shared messages SHR011-SHR016 appear in response to scrolling commands. | |
SHR011 | At bottom |
SHR012 | At top |
SHR013 | At left |
SHR014 | At right |
SHR015 | No data to display |
SHR016 | Scroll amount must be a positive integer. |
SHR020 | ON ATTN was hit, Use PF3 to QUIt |
SHR021 | <depends on the error> |
Description: Unexpected Model 204 error. Consult the Rocket Model 204 Messages wiki pages. | |
SHR022 | Unresolved enqueue conflict, reenter command or quit. |
SHR023 | Help text not found. Contact System Administrator. |
SHR024 | This PFkey or command is not supported. |
SHR025 | No defined action for ENTER key - please use PFkey or command-line. |
SHR026 | More text follows... |
SHR028 | Place search string on cmd line and press PF5 or precede with "LOC" |
SHR029 | Search string not located in text below. |
SHR031 | No help available from here |
SHR100 | <subsystem name>: Version <version> - Subsystem starting |
Description: This message is informational and is displayed by DICTIONARY and WORKSHOP facilities when they are started. | |
SHR110 | <subsystem name>: <err>: <error messages> |
Description: A fatal error has occurred that causes the facility to terminate. Record the message and contact the system manager or the administrator of the facility that you were running. | |
SHR111 | <subsystem name>: GTBL full, forced quit |
Description: The system has filled the global table during the execution of the facility. Contact the system manager or the administrator of the facility you were running. | |
SHR112 | WARNING: <filename> table B is xx% full. It has room for only yy additional records. |
SHR113 | INFORMATION: <filename> has an additional nn pages available. (FREESIZE = xx). |
SHR114 | WARNING: <filename> has no additional pages available (FREESIZE = 0). |
SHR115 | WARNING: <filename> table D is xx% full. It has room for only yy additional pages. |
SHR116 | WARNING: <filename> table A has had xx hashing retries. Time for REORG? |
SHR117 | WARNING: <filename> table C has had xx hashing retries. Time for REORG? |
DIC001 | Access to DICTIONARY facilities not allowed |
DIC002 | Enter a valid number |
DIC003 | Enter a valid command or a pf key |
DIC010 | Global variable table is full. Please exit session |
DDGEN messages
Number | Message text |
---|---|
DDG000 DDGEN | Run started |
DDG001 | No filename entered, DDGEN run stopped |
DDG002 | No workfile specified, DDGEN run stopped |
DDG003 | Read statement failed, Status is: |
DDG004 | Run has been cancelled |
DDG005 | Unresolved FIND conflict, run cancelled |
DDG006 | OPEN failed, skipping past filename: |
DDG007 | DDGEN utility end for this filename: |
DDG008 | File created under RELEASE 7.1 not supported in RELEASE 9.0 - File must be transformed to RELEASE 8.0 OR 8.1 before processing |
DDG009 | You are not authorized to view file parameters for |
DDG010 | Open statement failed, Status is: |
DDG011 | Error in reading procedure names, Status is: |
DDG012 | Error in reading procedure alias names, Status is: |
DDG01 | Illegal procedure name: |
DDG015 | Insufficient DDGEN release. DDGEN run cancelled. |
DDG016 | WARNING File created under 2.1 assumed. |
DDG017 | UNABLE TO PROCESS NON-TBO FILE WITH SYSOPT=4, CHANGE FILE TO TBO OR RESET SYSOPT. |
DDG018 | FICREATE UNRECOGNIZABLE. DDGEN RUN CANCELLED. |
DDG901 | Illegal error type, Status is: |
DDG999 | DDGEN RUN ENDED |
DDMIG Facility messages
Number | Message text |
---|---|
MIG001 | ON ATTN was hit. |
MIG002 | Unresolved enqueue conflict, unable to proceed. |
MIG003 | Invalid command syntax specified. |
MIG004 | @1 does not exist in the dictionary |
MIG005 | D204SYS is in use by another user, try again later. |
MIG006 | @1 is being updated in filemgmt. |
MIG007 | METADATA information already exists for @1. |
MIG008 | DATALINK information already exists for @1. |
MIG009 | No files have been exported. |
MIG010 | @1 has not been exported. |
MIG011 | All files have been deleted from D204SYS. |
MIG012 | @1 has been deleted from D204SYS. |
MIG013 | D204SYS has been updated since last LIST, do you want to continue? Y/N |
MIG014 | Parameter for IMPORT must be one of: ALL, CHECK, or a filename. |
MIG015 | Export record information incomplete, check status of D204SYS. |
MIG016 | All files have been deleted from D204SYS. |
MIG017 | BUG.........PAI INTO |
MIG018 | The parameter for DELETE must be ALL or a file name. |
MIG019 | Unable to open file D204SYS. |
MIG020 | Export VERSION number does not match Import VERSION. |
MIG021 | An invalid FILENAME was specified. |
MIG023 | @1 has already been exported. |
MIG024 | @1 has already been exported. |
MIG025 | @1 has staged commands. |
MIG026 | The following METADATA attribute fields are undefined: |
MIG027 | Report file does not exist or incorrectly specified. |
MIG028 | @1 already exists in the target-Dictionary. |
MIG029 | Duplicate entities found for @1. |
MIG030 | Error - check status of D204SYS. |
MIG031 | A file name must be specified for EXPORT. |
MIG032 | Import failed - the listed view(s) already exist in the dictionary. |
Dictionary Administration messages
Number | Message text |
---|---|
DIA001 | Select a valid command or a PF key |
DIA002 | Select a valid number |
DIA003 | Unresolved enqueue conflict, Reenter command or QUIt |
Description: The record you are trying to access is currently being used by another user. You may retry the command now or wait until user is finished. | |
DIA010 | Use PF6 to DELete the entity type or PF3 to QUIt |
DIA011 | Enter an account |
DIA012 | An entry for that account already exists |
DIA013 | There is no entry for that account |
DIA014 | Use an X to indicate selections |
DIA015 | Use PF12/END to update the DICTIONARY or PF3 to QUIt |
DIA016 | Account has been added |
DIA017 | Account has been updated |
DIA018 | Account has been deleted |
DIA019 | Maximum number of attributes has been added |
DIA020 | Maximum number of references has been added |
DIA021 | Enter entity type |
DIA022 | A definition for that entity type already exists |
DIA023 | Duplicate attribute value |
DIA024 | References cannot be added to system controlled entities |
Description: Users cannot update those entity types used by the system to maintain dictionary structure. | |
DIA025 | System reference types cannot be added |
Description: The reference type you are attempt to add has the same name as a system reference type. Select another name. | |
DIA026 | Entity type <TYPE> has been added |
DIA027 | Entity type <TYPE> has been updated |
DIA028 | Entity Type <TYPE> has been deleted |
DIA029 | There is no definition for that entity type |
DIA030 | Duplicate Reference |
DIA031 | Enter a path number |
DIA032 | Enter a valid path number |
DIA033 | Tagged items are invalid |
Description: No dictionary entries exist for the tagged entity types. | |
DIA034 | Path already exists |
DIA035 | The reference path has been defined |
DIA036 | The reference path has been replaced |
DIA037 | The reference path has been deleted |
DIA040 | UNQUALIFIED NAME cannot be added as a user attribute |
Description: UNQUALIFIED NAME is a system attribute and cannot be added as an attribute by a user. Select another name. | |
DIA041 | Invalid name for an attribute |
DIA100 | Enter valid entity type or 'all' |
Description: Either you have forgotten to name the entity type for which you want a report, or there is no dictionary entity for the named entity type. | |
DIA102 | Duplicate entity types found, contact Dictionary Administrator |
DIA103 | Specify output destination for report |
DIA104 | Specify Paper copy 'Y' or 'N' |
DIA105 | Specify Path Information 'Y' or 'N' |
DIA106 | Control Report Cancelled |
Description: You have used PA1 to halt the Entity and Path Report. | |
DIA107 | This entity type does not participate in a path |
DIA108 | There are no entity type definitions in the dictionary |
DIA109 | There are no reference paths defined in the dictionary |
DIA110 | There are no system relationships for this entity definition |
Description: You are on the Entity Type Maintenance screen and have selected to report on entity that has no system relationships listed. | |
DIA111 | There are no optional relationships for this entity definition |
Description: You are on the Entity Type Maintenance screen and have selected to report on an entity type that does not participate in any relationships with other entity types. | |
DIA112 | There are no system attributes for this entity definition |
Description: You are on the Entity Type Maintenance screen and have selected to report on an entity type that does not have any system controlled attributes. | |
DIA115 | DICTADMIN Inventory Report is being sent to the output device |
DIA201 | No facility record found for File Management |
Description: You are attempting to update File Management command execution options, but the dictionary cannot find a record for File Management. | |
DIA202 | Choose one or more command options |
DIA203 | Choose one default command option |
DIA204 | Indicate a USE file and/or a procedure file |
Description: You are on the File Management Commands Options screen and have selected the Inactive option without giving the name of a file to which procedures should be sent. | |
DIA205 | Use an X to select command options or defaults |
Description: This message is displayed on the File Management Options screen when a user enters any character other than an X to indicate a selection on the screen. | |
DIA206 | The default option must be one of the command options selected |
Description: This message is displayed on the File Management Options screen when the user selects an option that was not previously selected as one of the option the installation would support. | |
DIA207 | USE or PROC Filename must not begin with a number |
DIA208 | PROC Filename cannot begin with 'OUT' 'SYS' 'CCA' or 'TAPE' |
DIA209 | USE Filename cannot begin with 'SYS' 'CCA' or 'TAPE' |
DIA210 | Filename contains an invalid character |
DIA211 | Enter one option: add, rename, or delete |
DIA220 | No administration facilities are installed |
DIA221 | Warning, more than 8 admin facilities are installed |
DIA222 | Procedure name already exists. |
DIA223 | Enter new name for rename. |
DIA224 | Enter procedure name. |
DIA229 | Procedure name does not exist. |
DIA230 | Delete cancelled, press ENTER to continue |
DIA240 | No change to values on screen update not performed |
Description: You have not updated the screen, so no update to the dictionary is necessary. | |
DIA241 | VSAM TRANSPARENCY system tables have been changed |
DIA242 | Input must be numeric |
DIA243 | Input must be in valid range for table size |
DIA250 | The VSAMT control record was not found |
DIA255 | Update performed |
DIA900 | Entry not found in dictionary for this file or procedure. |
Dictionary Reports messages
Number | Message text |
---|---|
DIR001 | Select a valid option number |
DIR002 | Enter 'Y' or N for this option |
DIR004 | Enter a valid command or PF key |
DIR005 | No record with this type/name exists |
DIR006 | Null entry not allowed |
DIR007 | No such entity type exists |
DIR008 | Enter 'X' to select this option |
DIR009 | Null entity type not allowed |
DIR010 | This entity type cannot be widened |
Description: The WIDen command is available only for entity types with a file name prefix: RECORD, FIELD, FIELD GROUP, and PROCEDURE. | |
DIR011 | Select entity or enter QUIt |
DIR012 | Additional entities appear on next screen - Enter selection(s) |
Description: Indicates that the available entity types for the entity type report do not fit on one screen. Place an 'X' next to the entity type (s) you wish to select. Press enter to proceed to the next screen of entity types. When this message no longer appears, pressing enter will generate the report. | |
DIR015 | Select only one question and reenter |
Description: You have entered information for more than one question on the screen. Delete the information from one question, and press enter to generate the report. | |
DIR016 | Enter query criteria or enter QUIt |
DIR017 | Invalid entity type |
DIR018 | No such entry in dictionary |
DIR020 | Enter reference type |
DIR021 | No such reference type exists |
DIR022 | Select only 1 option and reenter |
Description: You have entered information for more than one option on the screen. Delete the information from one of the options, and press enter to generate the report. | |
DIR023 | Enter query criteria or enter QUIt |
DIR024 | Invalid entity type |
DIR025 | No such entry in dictionary |
DIR030 | Null keyword not allowed |
DIR031 | Invalid entity type entered |
DIR032 | Enter an option number - '1' through '4' |
DIR033 | Invalid attribute entered |
DIR034 | Attribute invalid with option selected |
DIR035 | No user written procedures are available |
Description: No user reports have been written for your installation. Press any PF key to exit from this screen and return to the Dictionary Reports main menu. | |
DIR036 | Additional reports appear on next screen |
Description: Indicates that all available user written reports do not fit on one screen. Place an 'X' next to the report you wish to select, if it appears on this screen. If it does not, press enter to proceed to the next screen of user written reports. | |
DIR037 | Report <report name> not found. Notify dictionary administrator. |
DIR038 | Enter an attribute |
Documentation messages
Number | Message text |
---|---|
DOC001 | Select a valid option number |
DOC002 | No such entity type exists |
DOC003 | No such entry exists |
DOC004 | Enter a valid command or pf key |
DOC005 | An entry with this name and entity type already exists |
DOC006 | Entity type is system controlled and can only be updated |
Description: The requested entity type is controlled by another facility. Entries of this type may not be added, renamed, copied, or deleted. Updating this entity type is allowed. | |
DOC007 | Enter 'Y' or 'N' for this option |
DOC008 | This entry is currently in use by another user |
DOC009 | Null entity type not allowed |
DOC010 | Request cannot be processed - required records are in use |
DOC011 | Documentation of this entity type is not authorized |
Description: You are not a user of the facility which controls this entity type. Therefore, you may not update entries of this type. | |
DOC012 | Enter an entry name |
DOC013 | Duplicate entries found for the tagged name. Contact system administrator. |
Description: DOCUMENT found more than one entry with this entity type and the name which has been tagged. Inform your system administrator of this error. | |
DOC014 | System controlled dummy entry - cannot be updated |
Description: The entry found is a dummy entry of a system controlled entity type. This entry may be updated only by the controlling facility. | |
DOC015 | Duplicate control records for this entity type. Contact system administrator. |
DOC016 | "Copy from or rename" name must be different than entry name |
Description: You entered the same name at the "Name:" prompt and the "Copy from or rename" prompt. Correct either name and reenter. | |
DOC017 | You are not authorized to modify any dictionary entries. |
DOC020 | Entry has been added |
DOC021 | Entry was not added - request was cancelled |
Description: You entered QUIt from Delete Entry. The new entry has not been saved. | |
DOC022 | Entry not added - required records in use |
DOC025 | Entry has been updated |
DOC026 | Entry was not updated - request was cancelled |
Description: You entered QUIt from Update an Entry. The new entry has not been saved. | |
DOC027 | Entry was not updated - required records are in use |
DOC030 | Entry has been deleted |
DOC031 | Entry has not been deleted - Request was cancelled |
Description: You entered QUIt from Delete. The entry has not been deleted. | |
DOC032 | Entry not deleted - it is in use by another user. Try later |
DOC033 | Entry was not found |
DOC040 | Entry has been copied |
DOC041 | Entry has not been copied - Request was cancelled |
DOC042 | Entry not copied - a required record is in use. Try later |
DOC043 | Entry not copied - entry to be copied was not found |
DOC044 | Entry not copied - Entity type not valid |
DOC050 | Entry has been renamed |
DOC051 | Entry has not been renamed - Request was cancelled |
DOC052 | Entry not renamed - a required record is in use. Try later |
DOC053 | Entry not renamed - entry to be renamed was not found |
DOC072 | Valid prefix commands are "I" and "D" |
DOC073 | Null entity type not allowed |
DOC074 | Entity type does not exist |
DOC075 | Number on command line is not a valid scroll amount |
DOC076 | Entry name is only valid widened item |
Description: You entered PF6 (WIDen) without placing the cursor on an entry name field. Place the cursor on the entry name you wish to widen and reenter the command. | |
DOC077 | This is a system reference and cannot be added |
Description: The reference type / reference name combination you have entered is controlled by another facility. You may not enter new references of this type. | |
DOC078 | References to staged entity types not allowed |
Description: You may not specify references to a STAGED FILE, STAGED FIELD, STAGED RECORD, or STAGED FIELD GROUP. Enter the non-staged version of the entity type instead. | |
DOC079 | Entry does not exist - dummy entry will be added |
Description: No entry exists with the specified entity type and name. If you save this reference, a dummy entry will be added for this entity. | |
DOC080 | Reference type is invalid for this entity type |
Description: You may not add new references that have not been defined by the administrator. | |
DOC099 | Entity type does not have a file name prefix and cannot be widened |
Description: The WIDen command is available only for entity types with a file name prefix: RECORD, FIELD, FIELD GROUP, and PROCEDURE. |
File Management messages
Number | Message text |
---|---|
FIM001 | On Attention was hit, use PF3 or QUIt to exit |
FIM002 | FIND CONFLICT, use PF3 to QUIt or re-enter command |
FIM003 | Correct all tagged items, press ENTER to view messages |
FIM004 | No changes have been made to the screen |
FIM005 | Widen is not a valid command for this item |
FIM006 | Invalid characters found in name |
FIM007 | Unrecognized value entered. Field reset to value. |
FIM008 | Enter the field name to be copied on the command line. |
FIM009 | Field not copied. Unable to locate field. |
FIM010 | Valid prefix marker is 'X' |
FIM011 | Valid prefix markers are 'X' and 'D' |
FIM012 | WARN: Field name will not be modified unless you mark the prefix |
Description: You have modified some attribute of a field without entering an X for the prefix. If you do not enter X, your modifications will not be saved. | |
FIM013 | Information on line has not been completed |
Description: You have not entered all the required information on a line on the screen. This error can occur on one of the list screens; for example, the Record Name List screen requires that you enter the record name and the number of records for that record. | |
FIM014 | Cursor is not on an input item |
FIM015 | Use PF3 to cancel the DELETE | INITIALIZE COMMAND Command or PF12 to Process |
Description: You have requested a DELETE or INITIALIZE command and must confirm your request by using PF12 to END or PF3 to QUIT. | |
FIM016 | Delete requested - use PF3 to cancel request |
FIM017 | CURSOR not on valid value cycling field. |
FIM018 | MIXED DBCS requires a minimum PREALLOCATED LENGTH of length bytes. |
FIM019 | WARN: MIXED DBCS requires a minimum length of @1 bytes. |
FIM020 | BUG: Number of datasets exceeds maximum allowed |
Description: File Management only allows 100 data sets to be internally contained in 1 file. Notify Technical Support. | |
FIM021 | BUG: An Invalid Fileorg was found on file entry |
Description: The Fileorg parameter in the file you are processing is not a valid Model 204 value. Notify Technical Support. | |
FIM022 | BUG: System error found in scrolling routine |
Description: There is incorrect information in the scrolling records in the M204TEMP record which has been passed from the Field List to the Field Attributes process. Notify Technical Support. | |
FIM023 | DBCS PREALLOCATED fixed length must be even. |
FIM024 | WARN: DBCS Average length must be even. |
FIM025 | Conflicting attributes ORDERED NUMERIC and MIXED/PURE DBCS. |
FIM026 | Conflicting attributes RECORD SECURITY and MIXED/PURE DBCS. |
FIM027 | Conflicting attributes INVISIBLE and AT-MOST-ONE. |
FIM028 | Conflicting attributes CODED FLOAT and PREALLOCATED. |
FIM029 | item1 has been copied to item2. |
FIM030 | A '+' is an invalid character for the tagged item |
FIM031 | A '.' is an invalid character for the tagged item |
FIM032 | You must enter a name to document |
FIM033 | WARN: You have marked the prefix but have not changed the name |
FIM034 | The tagged item(s) must be an integer |
FIM035 | item has been copied. |
FIM036 | At last field. |
FIM037 | At first field. |
FIM038 | NUMERIC VALIDATION must be selected with 1NF. |
FIM039 | DISABLE TBO must be selected with APPLY UPDATES DURING RF. |
FIM090 | BUG: No entry was found for entity entryname |
Description: The system has encountered a dictionary reference that has a missing entry record in METADATA. Contact your Dictionary Administrator. | |
FIM100 | Choose only 1: File, Field, Record or Field Group Maintenance |
FIM101 | File is staged for Delete or Initialize |
Description: You have requested an operation on a file that has been staged for deletion or initialization. If you wish to delete or initialize a file, you must first complete this process before invoking another command. | |
FIM102 | File has already been Created |
FIM103 | File is staged for Create, Recreate or Initialize |
Description: You have requested an operation on a file that has been staged for creation, recreation, or initialization. If you wish to create, recreate, or initialize a file, you must complete this process first before invoking another command. | |
FIM104 | File is staged with commands and cannot be deleted |
FIM105 | There is no existing file by this name |
Description: You have entered the name of a file that has not been created. | |
FIM106 | Field, Record and Field Group name only can be widened |
FIM107 | File is staged with commands and cannot be recreated |
Description: You have requested the RECREATE option on a file in which commands are staged. Until the staged commands in this file are executed, you cannot recreate the file. | |
FIM108 | File must have staged commands to proceed to Commands processing |
Description: A file needs a staged command, e.g., record DEFINE or file CREATE to proceed to the Execute or Delete Commands screens. | |
FIM109 | Increase or Decrease invalid for this file |
Description: You are requesting an increase or decrease to TABLE B or D for this file and the file does not yet exist; it is still staged for CREATE. | |
FIM110 | File is staged with commands and cannot be initialized |
Description: File Management does not allow you to initialize a file that already has commands staged for it. | |
FIM111 | The file is already Secured |
FIM112 | The file is not Secured - Desecure is invalid |
FIM113 | Field has already been defined |
FIM114 | File has no fields or records |
FIM115 | There is no field to Redefine, Delete, or Rename |
FIM116 | Field is staged for Delete - cannot Rename or Redefine (or delete) |
FIM117 | Field is staged for Define - cannot Rename, Redefine, or Delete |
FIM118 | There is no field by this name |
FIM119 | Record has already been defined |
FIM120 | Record has not been defined |
FIM121 | There is no production record to Redefine, Delete, or Rename |
FIM122 | Record is staged for Delete - cannot Rename or Redefine |
FIM123 | There are no valid records to redefine or rename |
FIM124 | There is no production record by this name |
FIM125 | There are no valid records to Delete |
FIM126 | Field Delete has already been requested |
FIM127 | Record Delete has already been requested |
FIM128 | There are no valid fields to Delete |
FIM129 | Field is staged with commands and cannot be Deleted |
Description: You have requested the DELETE option for a field that is staged for either RENAME or REDEFINE. | |
FIM130 | Record is staged with commands and cannot be Deleted |
Description: You requested the DELETE option for a record that is staged for either RENAME or REDEFINE. | |
FIM131 | The file is being changed by another user |
Description: You have requested a change to a file that is currently being changed by another user. | |
FIM132 | Define is the only valid choice for this file |
Description: You have requested a REDEFINE, DELETE or RENAME option for a new file that has not been created. | |
FIM133 | There is no field group to Rename, Delete or Redefine |
FIM134 | Field group has not been Defined |
FIM135 | Field group has been Defined |
Description: You are trying to define a field group that already exists. | |
FIM136 | The field group is staged for Define - cannot Rename, Redefine, or Delete |
FIM137 | The field group is staged for Delete - cannot Rename, Redefine, or Delete |
FIM138 | There are no field groups to Rename, Redefine or Delete |
FIM139 | A choice is required |
Description: You have not entered a filename or an option after the Field, File, Record or Field Group Maintenance prompts. | |
FIM140 | The item to be DOCUMENTed does not exist |
FIM141 | The file has been staged for SECURE |
FIM142 | The file has been staged for DESECURE |
FIM143 | ERROR: Duplicate file entries - see your Dictionary Administrator |
Description: More than one dictionary entry was found for the file. Notify your Dictionary Administrator. | |
FIM144 | There is no new or existing file by this name |
FIM145 | A FILENAME is required |
FIM146 | The file is staged for CREATE - cannot copy (ENTITY) |
FIM147 | Field groups require that fields be defined to a record |
FIM148 | Enter a valid option number for the tagged choice |
FIM149 | Filename must not begin with a number or special character |
FIM150 | May not copy to an existing file or staged file |
Description: You have entered the name of a file in after the COPY TO prompt which is the name of a previously created file or the name of a file that is staged for CREATE. | |
FIM151 | Choose copy option 1, 2, or 3 |
FIM152 | Enter filename for new file |
FIM153 | There are no fields or records on file to copy |
FIM154 | There are no fields on file to copy |
FIM155 | New file is locked to another user - cannot continue copy |
Description: Note: When an option number is entered in File Management that results in a conflict with SQL/204 DDF, you will receive one of the error messages below, FIM157-FIM160. | |
FIM156 | Reserved word invalid for field names |
FIM157 | File has been defined to SQLDDF, selection not allowed |
Description: The File Maintenance selection is not valid for a file that is defined to SQL/204 DDF. The selections not allowed are DELETE, RECREATE, COPY and INITIALIZE.
Enter a number that is valid or perform the operation from SQL/204 DDF. | |
FIM158 | Field is defined to SQLDDF, field selection not allowed |
Description: No field maintenance operations are allowed on a field defined to SQL/204 DDF. Perform maintenance on this field through SQL/204 DDF rather than FILEMGMT. | |
FIM159 | File has been defined to SQLDDF, ReCREATE not allowed |
Description: You cannot recreate a file defined to SQL/204 DDF. If file was created in SQL/204 DDF, drop the file from SQL/204 DDF and create a new file. If file was mapped from a FILEMGMT file, enter SQL/204 DDF and unmap the file. | |
FIM160 | File status incomplete in SQLDDF, file maintenance not allowed |
Description: The file was incompletely mapped from SQL/204 DDF.
The file status must be resolved through SQL/204 DDF. Enter the SQL/204 DDF and select the mapping option to complete the mapping of this file. If you are unable to map the file, see your system manager. | |
FIM161 | File created in SQLDDF must add fields thru alter in SQLDDF |
FIM162 | No AVERAGE LENGTH, 20 assumed for field(s) |
FIM163 | Field Attributes screen is display-only for RENAME/DELETE mode |
FIM164 | Select fields for RENAME/DELETE from the Field List screen |
FIM165 | The specified userid has no staged file commands |
FIM169 | Field is Date time Stamp, fieldname cannot be changed. |
Description: Datetime Stamp field corresponds to value of DTSFN and cannot be changed. | |
FIM170 | WARN: There is no valid Datetime Stamp field defined in file |
Description: The user is attemping to use a Datetime Stamp feature, but the file does not have the field defined. | |
FIM200 | Field|Record name missing |
Description: You have requested the Copy option for a field or record entry but have omitted a new record or field name. | |
FIM201 | Missing the 'Copy to' filename |
Description: You have not entered the name of the new file you are creating with the Copy option. | |
FIM202 | Field|Record names must be unique when copying to the same file |
Description: You have requested the Copy option for a field or record within a file and have entered the name of a field or record that already exists within that file. | |
FIM203 | There are no fields|records on file to copy |
FIM204 | Field|Record name does not exist |
FIM205 | Cannot copy all fields|records within the same file |
Description: You have requested the Copy option for all fields or records with in a single file. This option is only valid between files. | |
FIM206 | Field|Record name already exists |
FIM207 | All field|record names are already on 'Copy to' file - cannot copy |
FIM208 | WARN: Only able to copy nn fields/records to "Copy to" file |
FIM209 | WARN: DISABLE TBO marked as selected with APPLY UPDATES DURING RF |
FIM250 | Select one of ENTRY, SORTED, HASHED, or UNORDERED options |
FIM251 | REQ EVRY REC only valid for SORTED or HASHED files |
Description: You have selected the ENTRY or UNORDERED option as the type of file organization for the file you are creating. You must select the SORT or HASH option. | |
FIM252 | SORT/HASH KEY only valid for SORTED or HASHED files |
FIM253 | Select one of REUSE FIRST or APPEND FIRST options |
FIM254 | REUSE FIRST option is only valid WITH RDFS |
Description: You have selected the Reuse First option without selecting the Reuse Record Numbers option; Reuse First is only valid for a file created before Release 9.0 that is organized to reuse record numbers. | |
FIM255 | APPEND FIRST option is only valid WITH RDFS |
Description: You have selected the Reuse First option without selecting the Reuse Record Slots option; Reuse First is only valid for a file that is organized to reuse record slots. | |
FIM256 | TBO must be disabled if LOCK PENDING UPDATES are disabled |
Description: You have selected to Disable Lock Pending Updates, but have not chosen to Disable Transaction Backout. You must specify both options. | |
FIM257 | Select one of PUBLIC, SEMI-PUBLIC or PRIVATE options |
FIM258 | SELECT LEVEL must be between 0 and 255 |
FIM259 | READ LEVEL must be between 0 and 255 |
FIM260 | UPDATE LEVEL must be between 0 and 255 |
FIM261 | ADD LEVEL must be between 0 and 255 |
FIM262 | KEY FIELD NAME must be specified if RECORD SECURITY chosen |
FIM263 | KEY FIELD NAME is only valid if RECORD SECURITY chosen |
FIM264 | Make your selection with an 'X' |
FIM265 | FORMAT FILE must be either Y or N |
FIM266 | VERIFY FILE must be either Y of N |
FIM267 | AVG PROCNAME LEN must be between 1 and 255 |
FIM268 | PRCLDEF must be between 0 and 255 |
FIM269 | SORT/HASH KEY must be specified |
Description: You have selected a file organization of either Sorted or Hashed, but have not specified the hash key name. | |
FIM270 | If PUBLIC FILE, PRIVDEF must have ADHOC UPDATE privilege set |
Description: You have selected the Public access option for a file, but have not specified sufficient privileges for the default privilege class so that you can update the file.
If a PUBLIC file, PRIVDEF must have ADHOC UPDATE privileges set. | |
FIM272 | FICREATE is not a supported Model 204 release for this file |
FIM273 | KEY is only valid widen item |
FIM274 | Expected AVERAGE PAGES PER PROC requires a positive number |
FIM275 | Expected NUMBER OF PROCEDURES ENTRIES requires a positive number |
FIM276 | Expected NUMBER OR PROCEDURES has exceeded the DSIZE maximum |
FIM277 | Expected AVERAGE PAGES PER PROC has exceeded the DSIZE maximum |
FIM278 | Hash key and Record Security key cannot be the same field |
FIM279 | Unordered option invalid for files created before 9.0 |
FIM280 | File mode must be INACTIVE for files created before 9.0 |
FIM281 | INACTIVE (I) command mode not available - choose ACTIVE (A) |
FIM282 | ACTIVE (A) command mode not available - choose INACTIVE (I) |
FIM283 | WARN: REUSE FIRST marked as selected with RRN for a pre-9.0 file |
FIM284 | RRN not valid for ENTRY ORDER files - choose UNORDERED option |
FIM285 | 'A' or 'I' are the only valid choices |
FIM286 | WARN: UNORDERED marked as selected with RRN |
FIM287 | No command mode is valid - contact your Dictionary Administrator |
FIM288 | INACTIVE command mode is invalid - FICREATE must match current release |
FIM289 | PDSIZE must not exceed the maximum of 255, will be truncated to 255 |
FIM290 | FICREATE not supplied, specify item |
FIM291 | NONE may not be selected with 1NF or NUMERIC VALIDATION. |
FIM292 | TBO may not be disabled with the 1NF FILE MODEL. |
FIM293 | Files cannot be reset to 1NF FILEMODL. |
FIM294 | Files cannot be reset to NUMERIC VALIDATION FILEMODL. |
FIM295 | 1NF FILE MODEL requires AT-MOST-ONE field attribute. |
FIM296 | WARN: AT-MOST-ONE makes file inaccessible to pre 2.2 releases. |
FIM297 | WARN: Field level constraint not downward compatible past release 2.1 |
FIM298 | WARN: Redefine to AT-MOST-ONE may fail if field occurrence is gt 1. |
FIM299 | NUMERIC RANGE fields not allowed in 1NF FILE MODEL files. |
FIM300 | Filename cannot begin with 'OUT' 'SYS' 'CCA' or 'TAPE' |
FIM301 | Filename contains an invalid character |
FIM302 | NUMERIC RANGE fields not allowed in 1NF FILE MODEL files. |
FIM303 | FRV fields not allowed in 1NF FILE MODEL files. |
FIM304 | AT-MOST-ONE cannot be specified in a Non-TBO file. |
FIM305 | WARN: Turning off TBO with field level constraints defined to file. |
FIM306 | WARN: Multiply occurring fields present in a 1NF file. |
FIM307 | LANGUAGE Option must be US, JAPAN or TURKISH |
FIM308 | Optimized Field Extract must be an "N" or a "Y" |
FIM309 | PAGES must be between 1 and 16777216 |
FIM310 | Datetime Stamp parameter (DTSFN) not set in this system |
Description: In order to use the Datetime Stamp option, the parameter DTSFN must be set in the CCAIN to the fieldname that will be used for Datetime Stamp processing. | |
FIM311 | WARN: XAUTOINC will not be set if XSIZE = 0 |
FIM312 | You have selected Datetime stamp, press PF4 to define fields |
Description: On the Reset screen, the user selected the Datetime stamp option. This message directs the user to now go define the attributes associated with the Datetime stamp field. | |
FIM313 | Pages must be between 0 and 16,777,216 |
FIM314 | The maximum value for this field is 16,777,216 |
FIM315 | Use an X to select this field |
FIM316 | Option only valid with version 6.1 or later file |
FIM317 | This file is already defined as a Datetime Stamp file |
Description: The user is attempting to define the file as a Datetime Stamp file, but it already is a Datetime Stamp file. | |
FIM318 | WARN: must define field for DateTime Stamp |
Description: The user set FOPT=x'10', indicating a desire to use Datetime Stamp processing, but a field which corresponds to the value of DTSFN has not been defined to the file. | |
FIM319 | Enable Datetime Stamp must be an "N" or a "Y" |
Description: The user entered an invalid character in the Enable Datetime stamp input area. | |
FIM320 | Cannot disable Lock Pending Updates with Enable Date Time Stamp |
Description: The user attempted to select Disable Lock Pending Updates for a Datetime Stamp file. | |
FIM321 | Table X pages maximum value is 536,870,911 |
FIM322 | Option only valid with version 6.3 or later file |
FIM323 | Table X Auto Increase not valid with Sorted or Hash |
FIM324 | Only an X is allowed to select this field |
FIM325 | This option cannot be selected for a file created prior to version 6 |
FIM351 | Field names are only valid items to document |
FIM352 | Field names are only valid widened items |
FIM353 | Incorrect field name syntax |
FIM354 | Duplicate field name as entered |
FIM355 | Delete invalid for Sort, Hash, Record Security or DTS field |
FIM356 | Mark prefix with an 'X' before proceeding to ATTRIBUTES screen |
FIM400 | KEY must be Y or N |
FIM401 | INVIS must be Y or N |
FIM402 | DEFERRABLE must be Y or N |
FIM403 | NUMERIC RANGE (NR) must be Y or N |
FIM404 | FRV must be Y or N |
FIM405 | CODED must be Y or N |
FIM406 | FEW-VALUED must be Y or N |
FIM407 | MANY-VALUED must be Y or N |
FIM408 | NUMBER OF UNIQUE VALUES must be ALL or from 1 to 16,777,216 |
Description: The field you are defining or redefining is a Key, FRV, Numeric Range, Ordered, or Coded field and requires a value in Number of Unique Values for file sizing of the index space. You can specify ALL to indicate that every record contains a unique occurrence of the field's value. | |
FIM409 | NUMBER OF SIGNIFICANT DIGITS must be values 1 to 9 |
FIM410 | STRING must be Y or N |
FIM411 | BINARY must be Y or N |
FIM412 | FLOAT must be Y or N |
FIM413 | LEVEL must be an integer between 0 and 255 |
FIM414 | UPDATE AT END must be Y or N |
FIM415 | PREALLOCATED must be Y or N |
FIM416 | Length must be a positive integer between 1 and 255 |
FIM417 | MIN OCCURS must be an integer greater than zero |
FIM418 | MAX OCCURS must be an integer greater than zero |
FIM420 | Preallocated REPEATABLE must be an integer between 1 and 255 |
FIM421 | PREALLOCATED PAD must be between 00 and FF |
FIM422 | PHYSICAL FORMAT must be V or F |
FIM423 | SIGNIFICANT DIGITS LEADING must be Y or N |
FIM424 | SIGNIFICANT DIGITS TRAILING must be Y or N |
FIM425 | MIXED CASE must be Y or N |
FIM428 | INVISIBLE requires KEY, NUMERIC RANGE, or ORDERED |
FIM429 | Conflicting attributes: INVISIBLE and attribute |
FIM430 | Conflicting attributes: HASH and KEY |
FIM431 | Conflicting attributes: RECORD SECURITY and NON-KEY |
FIM432 | Conflicting attributes: INVISIBLE and PREALLOCATED |
FIM442 | Invalid PHYSICAL PICTURE |
FIM445 | MANY-VALUED requires CODED or FRV |
FIM446 | NUMBER OF UNIQUE VALUES requires KEY, FRV, CODED, ORDERED, or NR |
FIM454 | FLOAT requires length of 4, 8, or 16 |
FIM455 | Tagged items are WARNINGS. Press ENTER to view messages. |
FIM458 | PREALLOCATED requires a value for LENGTH |
FIM459 | PREALLOCATED requires a value for REPEATABLE |
FIM461 | Conflicting attributes: PREALLOCATED PAD and NON PREALLOCATED |
FIM462 | PHYSICAL PICTURE has invalid date format |
FIM463 | First character of PHYSICAL PICTURE is invalid |
FIM464 | PHYSICAL PICTURE is missing left parenthesis |
FIM465 | PHYSICAL PICTURE is missing right parenthesis |
FIM466 | PHYSICAL PICTURE must have number in parentheses |
FIM467 | PHYSICAL PICTURE exceeds maximum of setting |
FIM468 | Conflicting attributes: Variable format and Leading/Trailing 0's |
Description: Note: The following warning messages (noted by the WARN: prefix) inform you that you have not completed all the information for the field. You can execute the field command, but the sizing algorithm might not be accurate without the information you are missing. | |
FIM469 | WARN: A default length of 6000 will be stored for LOB sizing. |
Description: On the field attributes screen, when defining a LOB entry, if a length is not added for the field, a default of 6000 will be added. | |
FIM470 | WARN: A default length of 20 will be stored for Sizing. |
FIM471 | WARN: MIN OCCURS is null. Used by ACCESS. |
FIM472 | WARN: MAX OCCURS is null. Used by ACCESS. |
FIM473 | WARN: NUMBER OF UNIQUE VALUES is null. "ALL" is assumed. |
FIM474 | WARN: NUMBER OF SIGNIFICANT DIGITS is null. Used by Sizing. |
FIM475 | WARN: PHYSICAL PICTURE is null. Used by ACCESS. |
FIM476 | WARN: PHYSICAL FORMAT is null. Used by ACCESS. |
FIM479 | Serious error has occurred. Non-zero return code from SCRLGET |
Description: There is incorrect information in the scrolling records in the M204TEMP record which has been passed from the Field List to the Field Attributes process. Notify Technical Support. | |
FIM480 | WARN: Preallocated field invalid if data exists in the file |
Description: You are defining a field as Preallocated to a file that already has been created. This is illegal in Model 204. | |
FIM481 | MIN OCCURS is larger than MAX OCCURS |
FIM482 | FLOAT is invalid for a file created earlier than 8.0 |
Description: FLOAT is not a valid data type for files created with a version of Model 204 that is earlier than 8.0. | |
FIM483 | File created on 7.1 version is not transformed for FLOAT |
Description: You are trying to define a field with the FLOAT data type. However, the file was created with Model 204 release 7.1 and is not transformed for this data type. | |
FIM484 | Conflicting attributes: INVISIBLE and LENGTH |
FIM485 | Only VISIBLE fields can be renamed |
Description: You have requested to rename a field that is defined as invisible. | |
FIM493 | Conflicting attributes: HASH or SORT and not STRING |
FIM494 | HASH/SORT key cannot be PREALLOCATED if not req'd in every rcd |
FIM495 | WARN: RECORD SECURITY key average length is less than 10 |
FIM496 | HASH/SORT key cannot be multiply occurring |
FIM497 | WARN: Invalid PICTURE for NUMERIC RANGE - used by ACCESS |
FIM498 | ORDERED must be Y or N |
FIM499 | TREETYPE must be C or N |
FIM500 | LRESERVE must be an integer between 0 and 99 inclusive |
FIM501 | NRESERVE must be an integer between 0 and 99 inclusive |
FIM502 | SPLITPCT must be an integer between 1 and 100 inclusive |
FIM503 | IMMED must be an integer between 0 and 255 inclusive |
FIM504 | WARN: Tagged item is null. Used by Sizing |
FIM505 | Second page of attributes applies only to ORDERED fields |
FIM508 | SIZING PARAMETER must be an integer between 0 and 100 inclusive |
FIM509 | ORDERED invalid for file created earlier than 9.0 |
FIM510 | UNIQUE must be yes or no |
FIM511 | UNIQUE cannot be specified with DEFERRABLE |
FIM512 | WARN: Redefine to UNIQUE will fail if non-unique values present |
FIM513 | UNIQUE cannot be specified for Non-TBO file |
FIM514 | Datetime Stamp field cannot be UNIQUE. |
Description: On the field attributes screen, when defining a Datetime Stamp field, the attribute UNIQUE is not allowed. | |
FIM515 | DATETIME STAMP field cannot be a BLOB or CLOB. |
Description: On the field attributes screen, when defining a Datetime Stamp field, the attributes BLOB and CLOB are not allowed. | |
FIM550 | Record names are only valid items to document |
FIM551 | Record names are only valid widened items |
FIM552 | Incorrect record name syntax |
Description: You have entered a record name that does not meet the naming conventions for dictionary entries. It contains invalid characters or characters that are illegal as field names in a User Language programs. | |
FIM553 | Duplicate record name as entered |
FIM555 | Incorrect EXPECTED INCREASE Percentage |
FIM556 | EXPECTED INCREASE percentage must be numeric |
FIM557 | NUMBER OF RECORDS must be numeric and greater than zero |
FIM558 | Incorrect NUMBER OF RECORDS entered |
FIM559 | NUMBER OF RECORDS exceeds allowable maximum for the file |
FIM560 | Mark prefix with an 'X' before proceeding to Record Definition |
FIM601 | Recordname, Fieldname, Rectype Id Value are only valid widened items |
Description: You issued the WIDen command without placing the cursor on a record name, field name or Rectype Id Value. Place the cursor on the name and reissue the command. | |
FIM602 | % Field Occur must be numeric |
Description: You entered a non-numeric value in Percent Field Occurrence for a field. Re-enter the value. | |
FIM603 | Unique id must be X or D if it has previously been selected |
Description: The field you are working with has already been specified as a unique identifier for the record. If you do not want the field as a unique identifier, replace the X under the Unique Id prompt with a D. | |
FIM604 | Unique id must be X, '_' or EOF |
Description: The field you are working with has not been specified as a unique identifier for the record. If you want to specify the field as a unique identifier, you must enter X under the prompt; otherwise, delete the character you entered. | |
FIM605 | Rectype id must be X or D if it has previously been selected |
Description: The field you are working with has already been specified as a rectype id field for the record. If you do not want the field to be a rectype id field, type an X over the D. | |
FIM606 | Rectype id must be X, '_' or EOF |
Description: The field you are working was not specified as a rectype id field for the record. If you want to define the field as a rectype id field, type an X below the Rectype Id prompt. | |
FIM607 | Prefix for selected fields must be X, D, '_' or ' ' |
Description: Enter a D to remove the field from the record you are working on. Enter an X to modify the characteristics of the field. If you do not want to modify or delete it, blank out the invalid character. | |
FIM608 | Prefix for unselected fields must be X |
FIM610 | Invalid rectype id data value |
Description: The rectype id value you entered was not valid. Reenter the value. | |
FIM611 | No records have been selected for display |
FIM612 | Rectype id data value cannot be blank if Rectype id selected |
Description: You selected a field to be a rectype id field for the record. Enter the corresponding rectype id data value. | |
FIM613 | Enter an X to select Rectype id |
Description: You entered a rectype id data value without entering an X under the rectype id data value prompt. Enter an X to specify it as a rectype id field, otherwise the data value will be ignored. | |
FIM614 | Field must be deleted from Fld Grp before it is deleted from Record |
Description: This field is part of a field group in this record. File management will not automatically delete the field from the field group. You must go to the field group definition/redefinition and remove the field from its field group. Return to record definition/redefinition to remove the field from the record. | |
FIM615 | Preallocated fields cannot be deleted from the record definitions list |
FIM616 | Sort/Hash key required in every record cannot be deleted |
FIM617 | Preallocated fields must be present on 100 percent of records |
FIM618 | Date Time Stamp cannot be deleted from record |
Description: On the record definition screen, when attempting to delete a Datetime Stamp field from a record, the field cannot be deleted. | |
FIM619 | Prefix for unselected fields must be X, "_" OR " " |
FIM650 | Cursor is not on an input item |
FIM651 | Record and Field Group names are only valid documented items |
FIM652 | Incorrect Field Group name syntax |
FIM653 | Duplicate Field Group name as entered |
FIM654 | Field group must be saved before it is documented |
FIM655 | Mark Record prefix with an X before proceeding to FldGrp Defn |
FIM656 | You have not marked or entered any new field groups to define |
FIM657 | Mark a FldGrp prefix with an X before proceeding to FldGrp Defn |
FIM658 | You must mark field groups and records to enter FldGrp Defn |
FIM659 | There are no field groups marked |
FIM660 | Field groups require that fields be defined to a record |
FIM661 | WARN: Field groups will not be saved unless you mark a prefix |
FIM662 | WARN: You must proceed to FldGrp Definition to save any changes |
FIM663 | You have marked more records than field groups to define |
FIM664 | Record and Field Group names are only valid widened items |
FIM675 | Record name, Fld Grp name, Field name are only valid widened items |
Description: You have issued the WIDen command without placing the cursor on a record name, field group name, or field name. Place the cursor on the desired name and reissue the command. | |
FIM676 | Select a Field Group by marking it with an X |
Description: You have entered the SWItch command without selecting another field group to define or redefine. Place an X in the prefix area next to the field group you want to work on and reenter the command. | |
FIM677 | WARN: Avg Occurs value for all fields in the group do not match |
Description: File Management expects the average number of occurrences for each field in a field group to be the same. You may define field groups whose fields have different average occurs values; however, you will receive this warning message. You can ignore the message if you want to proceed defining or redefining field groups. | |
FIM678 | Prefix for selected fields must be D |
Description: You have entered an invalid character in the prefix area or a field in a field group. Enter a D to remove the field from the field group or blank out the invalid character. | |
FIM679 | Prefix for field groups must be X |
Description: You have entered an invalid character in the prefix area of a field group name. Enter an X to define or redefine a field group or blank out the invalid character. | |
FIM680 | Select a field group and SWItch before selecting fields |
Description: You have attempted to select fields for a field group but you have not selected a field group. Delete the X's you have filled in, return to the "Remaining Field Groups" section, select a field group and enter the SWItch command (PF9). Return to the "Remaining Fields in Record" section and select the fields in this field group. | |
FIM681 | WARN: ACCESS cannot use singly occurring fields |
FIM725 | Transaction Backout file may not disable LPUs |
Description: You are requesting the Disable Lock Pending Update option for a file which is specified to run with Transaction Backout. | |
FIM726 | BRESERVE cannot be larger than (PAGESIZE - 40) |
FIM727 | DRESERVE must be between 1 and 100 |
FIM728 | Can only select RECORD SECURITY during CREATE |
FIM800 | BSIZE is non-numeric, negative or exceeds allowable maximum |
FIM801 | BSIZE EXCEEDS ALLOWABLE MAXIMUM - FILE REUSES RECORD SLOTS |
FIM802 | New BSIZE cannot be less than the number of TABLEB pages used |
Description: You cannot decrease Table B to a value less than the number of pages used in the file (BHIGHPG). | |
FIM803 | DSIZE is non-numeric, negative or exceeds allowable maximum |
FIM804 | New DSIZE cannot be less than the number of TABLED pages used |
FIM805 | Dataset information is incomplete |
Description: When you are adding new data sets to a file, you must supply the DD name, data set name, device type, and trk/blks. These are used by sizing and as part of the CREATE and INCREASE commands. | |
FIM806 | DDname cannot begin with OUT SYS CCA or TAPE |
FIM807 | Duplicate DDnames not allowed |
FIM808 | Dataset name contains an invalid character |
FIM809 | Dataset name is missing a parenthesis |
FIM810 | Duplicate Dataset names not allowed |
FIM811 | Invalid device type |
FIM812 | Track or block allocation is not numeric |
FIM813 | Total table sizes too large for file |
Description: You requested to INCREASE a file and the addition of all new table sizes exceeded the allocated pages for the current file (including FREESIZE). | |
FIM814 | Password required |
Description: The file you are requesting to INCREASE or DECREASE requires a read-only password. The password is needed so you can VIEW the file's BHIGHPG and DPGSUSED parameter values. | |
FIM815 | Insufficient FREESIZE for Table B increase |
FIM816 | Insufficient FREESIZE for Table D increase |
FIM817 | DDname contains an invalid character |
FIM818 | DDname is the name of a file or staged file |
FIM819 | DDname cannot begin with a number |
FIM820 | BSIZE must be an integer between 1 and 16777216 |
FIM821 | DSIZE must be an integer between 1 and 16777216 |
FIM822 | Insufficient FREESIZE for Table E increase |
Description: On the sizing screen, an increase in ESIZE must be less than or equal to what is available in FREESIZE. | |
FIM823 | Table E decrease cannot be less than 20 |
FIM824 | Table X cannot be decreased to 0 |
FIM825 | Table X cannot exceed 536870911 |
FIM826 | Table X cannot be decreased to 0 without recreate |
FIM827 | ESIZE is non-numeric, negative or exceeds allowable maximum |
FIM828 | You are not authorized to view file parameters |
FIM829 | New ESIZE cannot be less than the number of TABLEE pages used |
FIM830 | No NUMBER UNIQUE VALUES, 1 per record assumed for field(s) |
FIM831 | Calculated Esize too large - maximum assumed |
FIM832 | XSIZE can only be used with entry order and unordered files |
FIM833 | XSIZE cannot be zero if XAUTOINC is set |
FIM834 | BSIZE must be an integer between 1 and 98304 |
FIM850 | BRESERVE too large for table B page |
Description: BRESERVE must be no longer than (PAGESZ-40). | |
FIM851 | DRESERVE must be between 0 and 100 |
FIM852 | Page size must be 6184, 7208, 3624, or 3368 |
FIM853 | FVFPG parameter must be between 1 and 65,536 |
FIM854 | MVFPG parameter must be between 1 and 65,536 |
FIM855 | BRECPPG * BSIZE must not exceed 16,777,216 |
FIM856 | CSIZE must be an integer between 1 and 65,536 |
FIM857 | ASIZE must be between 1 and 196,605 |
FIM858 | BEXTOVFL pages in error |
Description: You are creating a sorted file and the values of the stored index (BEXTOVFL) extra overflow pages (BPGPOVFL), master overflow pages and (BPGPMSTR) master sort pages are not specified correctly. Refer to the chapter on sorted files in the Rocket Model 204 documentation wiki "Model 204 files" pages. | |
FIM859 | BPGPOVFL pages in error |
FIM860 | BPGPMSTR pages in error |
FIM861 | Sorted files are required to have master and overflow pages |
Description: You are working with a sorted file and have not completed the BEXTOUFL, BPGPOVFL and BPGPMSTR parameters. | |
FIM862 | ATRPG * ASTRPPG exceeds 4000 |
FIM863 | ATRPG, FVFPG, and MVFPG do not equal ASIZE |
FIM864 | PDSIZE and PDSTRPPG required if using procedures |
Description: You have specified that the file you working on will contain procedures (EXPECTED PROCS) or there are procedures entries linked to it in the dictionary, and the parameters used to size the procedure dictionary (PDSIZE/PDSTRPPG) are null. | |
FIM865 | FREESIZE parameter in error |
FIM866 | WARN: Total number of records is 0, default table sizes used |
Description: When calculating the file sizes, the system did not find any records linked to the file you are working on or found no value in the Total Number of Records on the file entry. The file was sized using the default table sizes in Model 204. See the parameter descriptions for ASIZE, BSIZE, CSIZE, and DSIZE for the default sizes. | |
FIM867 | ASTRPPG must be numeric, between 1 and 4,000 |
FIM868 | Calculated Dsize too large - maximum assumed |
Description: In calculating DSIZE during sizing, you exceeded the maximum value for DSIZE, so sizing used the maximum value. See the parameter description of DSIZE for details. | |
FIM869 | ATRPG must be numeric, between 1 and 4,000 |
FIM870 | PDSIZE must be numeric, between 1 and 255 |
FIM871 | PDSTRPPG must be numeric, between 1 and 256 |
FIM872 | BRESERVE must be numeric and less than PAGESZ - 40 |
FIM873 | Calculated Csize too large - max assumed |
Description: When you were sizing the file, the CSIZE size you calculated exceeded the Model 204 maximum, the maximum value was used. See the CSIZE parameter description for details. | |
FIM874 | WARN: tracks not recalculated -- old value not changed |
Description: File Management calculates disk requirements only if there is one data set per file. If there are more than one data sets per file, you must enter the track or block allocation next to the corresponding device and data set name. | |
FIM875 | BRECPPG must be an integer value between 1 and 9999 |
FIM876 | PDSIZE has changed, you may want to ReCREATE the file |
FIM877 | ASIZE has changed, you may want to ReCREATE the file |
FIM878 | Press ENTER to view multiple messages |
FIM879 | BSIZE increase is larger than HASHED table limit |
FIM880 | CSIZE has changed, you may want to ReCREATE the file |
FIM881 | Maximum number of preallocated fields is exceeded |
FIM882 | Default values assumed for blank screen items |
Description: You have chosen to redisplay a screen and all the null items on it were replaced with their default values. | |
FIM883 | FREESIZE recalculated for new table sizes |
FIM884 | BREUSE must be between 1 and 100 |
FIM885 | DPGSRES WITH %NUMTXT WITH 0 and 32767 |
FIM887 | DPGSRES must be between 0 and 32767, and no larger than DSIZE |
FIM900 | DSIZE must be an integer value between 1 and 65536 |
FIM901 | USE file is needed for a report |
Description: You must specify a USE (directed output) name at the USE prompt on the screen. Type in the appropriate USE name and re-execute the command. | |
FIM902 | Active or Inactive modes must be selected for command execution |
Description: You must select Active or Inactive mode for the command you wish to execute. | |
FIM903 | USE file is not defined, nothing printed |
Description: The USE (directed output) name that you specified is not defined. Check to make sure the name of the file is spelled correctly. | |
FIM904 | The only valid prefix value is X(select) | D(delete) |
Description: You have typed something other than X or D on screen where only X (execute) or D (delete) are valid. Check the prefix areas of all lines and try again. | |
FIM905 | Item definition must be complete before selecting a command |
Description: You selected a command that cannot be executed until you finish defining an item. Transfer to the appropriate File Management screen to complete the definition. | |
FIM906 | Choose only procedure or USE output for commands |
Description: You have chosen both procedure and USE output on a screen where only one of these options is valid. Correct the screen and try again. | |
FIM907 | Unable to open procedure file to store commands (for IN option) |
Description: The procedure file you specified cannot be opened. Check the file name and password. | |
FIM908 | Unable to store commands in procedure file (for IN option) |
Description: The privileges specified for the procedure file you are using do not allow you to define any new procedures. Check the file name and password. | |
FIM909 | ON ATTN was hit, use Pf3 to QUIt |
FIM910 | error-dependent message |
Description: File Management encountered a Model 204 error. You can find the Model 204 error explanation elsewhere in this manual. | |
FIM911 | Unresolved enqueue conflict, reenter command or quit |
FIM912 | Choose only 1 mode for execution of commands |
Description: You are on a screen which permits only ACTIVE or INACTIVE mode. Check to make sure you have requested only one of these commands. | |
FIM913 | Scroll amount must be a positive integer |
Description: You must use a null (for a full screen) or a positive integer in a scroll command argument. Check the numbers and try again. | |
FIM914 | No space available in file to store the procedure |
Description: There is insufficient space in TABLE D of the specified file to store the procedure with commands. Either choose a different file name or free space in the specified file by deleting procedures in the file. | |
FIM915 | FILEMGMT subsystem files are invalid for storing procedures |
Description: Files used for storing command procedures in inactive mode cannot be chosen from among files used by the FILEMGMT subsystem. These files include: METADATA, DATALINK, M204PROC, and M204TEMP. Change the name of the procedure file and try again. | |
FIM916 | Use DICTADMIN facility to define File Management execution options |
Description: The Dictionary Administration facility enables you to define execution options for &fm. commands. If no options are defined as valid, no commands can be executed. | |
FIM917 | USE name may not begin with 'SYS', 'CCA', or 'TAPE' |
FIM918 | Procfile name may not begin with 'OUT', 'SYS', or 'CCA' |
FIM930 | Report printed |
Description: This is an informational message indicating that a print command has been executed. Check the STATUS field for the command to determine whether the dictionary has been updated. | |
FIM931 | Selected commands deleted |
Description: This is an informational message indicating that the commands you selected have been deleted. Check the STATUS command to determine whether the dictionary has been updated. | |
FIM932 | Selected commands executed successfully |
Description: The commands selected have been executed without errors. All command statuses should be "successful." This message appears only in Active Immediate mode. The dictionary has been updated to reflect the changes for each successful command. | |
FIM933 | Selected commands pending |
Description: The commands selected have been marked as pending for active execution in batch mode. The dictionary has not been updated to reflect the changes. | |
FIM934 | Selected commands generated |
Description: The commands selected have been generated through dictionary output or to a procedure. The dictionary has not been updated to reflect the changes. | |
FIM935 | No commands selected |
Description: You entered the EXEcute/DELete command but did not select any commands for execution or deletion. Insert an X (for EXEcute) or a D (for DELete) to select each command. | |
FIM936 | Selected commands executed, check command statuses for errors |
Description: The commands selected have been executed, but some or all of the commands might have errors. Check the STATUS field for each command to determine whether the command was successful or not. The dictionary has been updated to reflect the changes for only the successful command. | |
FIM937 | Warning: Subsystem(s) use file ! PF3=Quit, PF6/12=Process |
FIM940 | M204 command: text of Model 204 command |
Description: This is an informational message that appears in the audit trail only. It is generated for each Model 204 command generated by the File Management facility. | |
FIM941 | Blinking fld is AVG LEN MULTIPLIER H=Hundreds,T=Thousands, M=Millions |
FIM942 | Warn: ESIZE must be greater than 20. |
Description: The minimum size for a BLOB is > 20. | |
FIM943 | Avg Length must be between 1 and 9999 |
FIM944 | Datetime Stamp field cannot be INVISIBLE |
Description: On the field attributes screen, when defining a Datetime Stamp field, the attribute INVISIBLE is not allowed. | |
FIM945 | XSIZE can only be used with entry order and unordered files |
FIM946 | Date Time Stamp cannot be multiply occurring |
Description: On the field attributes screen, when defining a Date Time Stamp field, the attribute OCCURS must be one. | |
FIM947 | Only values of 0 or 1 are valid for RECRDOPT |
Description: On the sizing screen, only values of 0 or 1 are valid for RECRDOPT. | |
FIM948 | XSIZE value is outside range of allowed values 0 to 536870911 |
Description: On the sizing screen, XSIZE must be between 0 and 536870911. | |
FIM949 | File must be recreated to change XSIZE |
Description: On the sizing screen, when updating sizing information, if you now want to use TableX, the file must be recreated. | |
FIM950 | XRESERVE, XRECPPG and RECRDOPT not valid without XSIZE |
Description: On the sizing screen, XSIZE must have a non-zero value before setting XRESERVE, XRECPPG or RECRDOPT. | |
FIM951 | XRESERVE, XRECPPG must be > 0 when XSIZE is > 0 |
Description: If XSIZE is a positive non-zero number, then XRESERVE and XRECPPG must also be positive, non-zero numbers. | |
FIM952 | Insufficient FREESIZE for TABLEX increase |
Description: When attempting to increase the size of Table X, there must be sufficient pages available in FREESIZE to handle the increase. | |
FIM953 | XRESERVE valid values from 0 to 6140 |
Description: On the sizing screen, XRESERVE must be between 0 and 6140. | |
FIM954 | Trks/Blks not filled in -- Use PF9 to size |
FIM955 | XSIZE cannot be zero if AUTOINC is set |
Description: On the File Definition - Organization screen, a non-zero value was entered for "Table X Auto Increase Pages". Revisit that screen and reset that value to zero before attempting to change XSIZE to zero on the sizing screen. | |
FIM956 | ESIZE must be an integer value between 1 and 1073741823 |
FIM957 | Insufficient FREESIZE for table E increase |
FIM999 | The Documentation Facility has not been started |
SUBSYSMGMT error messages
Number | Message text |
---|---|
SUM001 | Global table is full. Please QUIT. |
Description: The value of LBTBL is not sufficient for the subsystem application. LBTBL must be set to at least 100. | |
SUM002 | No changes have been made to the screen. |
Description: Type in input and press Enter or use a PF key to move to another screen. | |
SUM003 | Subsystem definition incomplete. Define OPERATION. |
SUM00 | Subsystem definition incomplete. Define PROCEDURE. |
SUM005 | Subsystem definition incomplete. Define SYSCLASS. |
SUM006 | Subsystem definition incomplete. Define USERDEF. |
SUM007 | Subsystem is active. Cannot modify SYSCLASS. |
Description: Issue STOP to change subsystem classes. | |
SUM008 | Unresolved enqueue conflict. Try again or QUIT. |
Description: Some part of the subsystem definition is being used by a subsystem or DICTIONARY user. | |
SUM009 | The default subsystem class is displayed as bright. |
SUM010 | CCA subsystem. Can only use USERDEF or user activity. |
Description: The definition of user classes is the only part of the subsystem definition that can be modified. The entire definition can be browsed. | |
SUM011 | ON ATTENTION was hit. Use PF3 to QUIT. |
SUM012 | Subsystem definition incomplete. Define FILEUSE. |
SUM051 | Not a valid subsystem activity selection. |
SUM052 | Not a valid user activity selection. |
SUM053 | PFkey or command only valid with subsystem Add, Modify, or Browse. |
SUM054 | Copy/Rename name is not valid with this selection. |
SUM055 | New subsystem name is required. |
SUM056 | Subsystem name is not valid with this selection. |
SUM057 | Subsystem name is required. |
SUM058 | Copy/Rename account is not valid with this selection. |
SUM059 | Copy/Rename account is not required for this selection. |
Description: Copy/Rename field has a value but is not needed for the selection. | |
SUM060 | Subsystem does not exist. |
SUM061 | Subsystem already exists. |
SUM062 | New subsystem already exists. |
SUM063 | User account is not valid with this selection. |
SUM064 | User account is required. |
SUM065 | Copy/Rename account is required. |
Description: Enter the name of the account to be copied/renamed. | |
SUM066 | User account does not exist. |
SUM067 | New user account already exists. |
SUM068 | Deletion CANCELLED. |
SUM069 | ____ copied to _____. |
SUM070 | Subsystem ______ deleted. |
SUM071 | Subsystem ______ renamed to ______. |
SUM072 | Account ______ copied to _______. |
SUM073 | Account ______ deleted. |
SUM074 | Account ______ renamed to _______. |
SUM075 | Invalid option. Enter QUIT or END. |
SUM076 | Invalid command, Pfkey, or no activity selected. |
SUM077 | Subsystem name contains illegal characters. |
SUM078 | New subsystem name contains illegal characters. |
SUM080 | No privileges have been assigned to @1. |
Description: An attempt was made to copy/rename/delete an account that has not been assigned ADMIN privileges. Check spelling of account name or assign user privileges. | |
SUM081 | No subsystems match specified name or pattern: @1. |
Description: Check spelling of name or pattern. | |
SUM082 | Value must be Y or N. |
SUM084 | Cannot delete CCA subsystems. |
SUM093 | PFkey or command only valid with MODIFY option. |
Description: On the main SUBSYSMGMT screen, the user pressed PF7/CMDprv and selected an option other than MODIFY. MODIFY is the only valid option for PF7/CMDprv. | |
SUM094 | Subsystem name or pattern is required. |
Description: On the main SUBSYSMGMT screen, the user pressed PF7/CMDprv and did not specify a name or pattern in the Subsystem Name field. | |
SUM096 | Refine criteria: # of subsystems classes exceeds max(1000). |
Description: On the Command Privileges screen, the max number of subsystem classes that may be processed at one time is 1000. If a user specifies a pattern in the Subsystem Name field that results in a list that exceeds 1000, then this message is displayed. | |
SUM098 | Press 12/END to make changes or 3/QUIt to exit. |
Description: On the Command Privilege screen, this message is displayed when a user hits PF3/QUIt in order to confirm that the user wants to quit without any updates applied. | |
SUM099 | No value specified for Subsystem Name. |
Description: On the Command Privilege screen, this message is displayed when the user hits PF4/LISt and does not supply any value in the Subsystem Name field. | |
SUM099 | No value specified for Subsystem Class. |
Description: On the Command Privilege screen, this message is displayed when the user hits PF4/LISt and does not supply any value in the Subsystem Class field. | |
SUM099 | SYNTAX ERROR IN PATTERN '<pattern>' NEAR CHARACTER <n> |
Description: On the Command Privilege screen, this message is displayed when the user hits PF4/LISt and supplies an invalid pattern the Subsystem Name or Subsystem Class fields. | |
SUM100 | Invalid status. Must be 1, 2, or 3. |
SUM101 | Value must be Y or N. |
SUM102 | Invalid hex value. |
Description: The value entered contains an invalid character or is not within the range of X'00' to X'FF'. | |
SUM103 | PUBLIC invalid with more than 1 Delete all but one class. |
Description: Use SYSCLASS to delete. using the SYSCLASS screen or use a semipublic or private status. | |
SUM104 | The value entered must be from 1 to 99999. |
SUM150 | Null values are not valid. |
SUM151 | Duplicate values for prefixes are not valid. |
SUM152 | Procedure names must begin with a prefix. |
SUM153 | Warning -Use of global XFER prohibits subsystem transfer. |
Description: XFER is a reserved variable that cannot be used on the Procedure Specifications Screen. | |
SUM154 | Global variable names must be identical. |
SUM155 | Global variable names must not contain ??, ?$, or ?&. |
SUM200 | The default subsystem class cannot be deleted. |
Description: A default class is required for public or semipublic subsystems. Do not delete this class or change the status to public. | |
SUM201 | Only one subsystem class is valid |
Description: The valid class is for public subsystems. default. Change the status to semipublic or private for multiple classes. | |
SUM202 | Procedure file must be entered. |
SUM203 | Value tagged is not valid or beyond acceptable range. |
Description: On the Command Privilege screen, the user entered an invalid value in the selection field for the Subsystem Name or Subsystem Class. The only valid value for the selection field is "x". | |
SUM204 | File names must start with a letter. |
SUM205 | Deferred ddnames must start with TAPE. |
SUM206 | Subsystem class already defined. |
SUM207 | Duplicate file on this screen. |
SUM208 | File already defined for this sub- system class. |
SUM209 | File name cannot have blanks. |
SUM210 | At first subsystem class. |
SUM211 | At last subsystem class. |
Description: Attempt made to browse beyond the last subsystem class. | |
SUM212 | PF10/PREV not available. |
SUM213 | A value must be specified for NUMLK when group value is Y. |
SUM214 | GROUP value must be Y when a value is specified for NUMLK. |
SUM215 | File name cannot begin with CCA, OUT, SYS, or TAPE. |
SUM216 | Deferred ddnames cannot have blanks. |
SUM250 | Previous subsystem class selected was number: |
SUM251 | No users are defined to this sub- system class. |
SUM252 | No subsystem classes defined. Use SYSCLASS. |
Description: Define subsystem classes by using the SYSCLASS screen before defining users for the classes. | |
SUM253 | No subsystem classes defined. |
SUM254 | Subsystem class number must be numeric. |
SUM255 | Subsystem class number cannot be zero or a negative number. |
SUM256 | Subsystem class number is greater than the number of classes. |
SUM257 | Account(s) already defined or duplicated on this screen. |
SUM258 | Default class is the only class. Cannot define users for it. |
SUM259 | Users cannot be added to the default subsystem class. |
SUM300 | A FIND conflict has occurred for this account. |
SUM301 | <n> Subsystem(s) enqueued. Press 6/DISplay to list. |
Description: On the Command Privilege screen, this message is displayed to inform the user that there are a number of subsystems that are not displayed on the list and cannot be updated due to enqueuing conflicts. | |
SUM302 | Classes enqueued, 6/DISplay or 12/END to perform partial update. |
Description: On the Command Privilege screen, this message is displayed to inform the user that there are a number of classes that cannot be updated at this time due to enqueuing conflicts. The user has the option to perform a partial update such that the Command Privileges for the classes that are not enqueued are updated. In addition, the user has the option to display the list of classes that are enqueued and cannot be updated. | |
SUM303 | <n> Class(es) about to be updated, press 12/END to confirm update |
Description: On the Command Privilege screen, this message is displayed when the user presses PF12/END in order to inform the user about the number of Subsystem Classes that are about to be updated. | |
SUM304 | No update, Command Privileges not changed for selected subsystems |
Description: On the Command Privilege screen, the user pressed PF12/END to update the Command Privileges but either the privileges were not changed or there were no Subsystem Classes that were selected for update. | |
SUM305 | Warning! 11/UPDate must be pressed now to save changes. |
Description: On the Command Privilege screen, the user pressed PF4/LIST to obtain a new list but the command privileges for the previous list were not saved. | |
SUM306 | Classes enqueued, 6/DISplay or 11/UPDate to perform partial update. |
Description: On the Command Privilege screen, this message is displayed to inform the user that there are a number of classes that cannot be updated at this time due to enqueuing conflicts. The user has the option to perform a partial update such that the Command Privileges for the classes that are not enqueued are updated. In addition, the user has the option to display the list of classes that are enqueued and cannot be updated. | |
SUM307 | <n> Class(es) about to be updated, press 11/UPDate to confirm update. |
Description: On the Command Privilege screen, this message is displayed when the user hits PF11/UPDATE in order to inform the user about the number of Subsystem Classes that are about to be updated. | |
SUM308 | Must use 4/LISt when changing Subsystem or Class patterns |
Description: The user entered a new value in the Subsystem Name or Subsystem Class field and pressed an invalid key. | |
SUM309 | Enter a valid command or pfkey. |
SUM400 | Contact System manager, no privileges have been assigned to user ID. |
Description: User must be assigned administrative privileges to use SUBSYSMGMT. | |
SUM401 | User does not have privileges for the selected option. |
Description: Only valid options for the assigned administrative privileges may be selected. | |
SUM402 | User has not been granted privileges for this subsystem. |
Description: System manager has not assigned the user administrative privileges for the selected subsystem. | |
SUM403 | @1 has been deleted from D204SYS. |
SUM404 | Select a valid PF KEY for Add, Modify, Browse. |
Description: Must select one of: PF2,PF4,PF5,PF6,PF9 for this option. | |
SUM405 | Value must be U or A. |
SUM406 | Duplicate METADATA entries for subsystem. |
SUM408 | Subsystem pattern is not valid for this selection. |
Description: Remove name or pattern and retry. | |
SUM409 | D204SYS is in use by another user. |
Description: Another user is executing an import/export command. | |
SUM410 | Import VERSION parameter does not match Export VERSION parameter. |
Description: Import/export must be between the same version of Model 204. | |
SUM411 | Unable to IMPORT @1, CCASYS fields undefined. |
Description: The subsystem to be imported contains fields which are not defined in the destination dictionary. | |
SUM412 | Cannot export CCA subsystems. |
SUM413 | @1 has not been exported. |
Description: Export the subsystem before importing. | |
SUM414 | Unable to IMPORT, fields undefined for @1 METADATA entry. |
SUM415 | Unable to locate import data. |
SUM416 | @1 is being updated by another user |
Description: Import/export attempted on a subsystem that is being updated by another user. | |
SUM417 | @1 Imported. Dummy entries were added for Procedures and/or Files. |
Description: The specified files from the import subsystem did not previously exist in the destination dictionary. | |
SUM418 | @1 has been @2. |
SUM419 | Reenter the command to confirm the deletion. |
SUM420 | No subsystems located or user does not have view privileges. |
Description: No subsystems have been exported or the user does not have ALL privileges for any of the exported subsystems. | |
SUM421 | No subsystems have been exported. |
SUM422 | Unable to open D204sys. |
Description: An error occurred while trying to open D204SYS. | |
SUM423 | ERROR - check status of D204SYS. |
SUM424 | No subsystems were located. |
SUM425 | Select privileges with an 'X'. |
SUM426 | Only assign one of: ALL, MODIFY, or BROWSE privileges. |
Description: A user has been assigned more than one admin privilege for the tagged subsystem. | |
SUM427 | Enter a subsystem name to locate. |
Description: Enter the subsystem name on the command line and press PF5. | |
SUM428 | Unable to locate subsystem: @1. |
SUM429 | WARNING: updates will not be saved. Reenter command to exit. |
SUM430 | Administrative privileges have been updated for @1. |
SUM431 | WARNING: all Userids will be deleted from @1. Reenter command. |
SUM432 | No users were located for SCLASS: @1 in subsystem @2. |
SUM433 | WARNING: @1 duplicates found. Reenter to execute. |
Description: A user ID to be copied already exists in an SCLASS. Select preview to display the list. | |
SUM434 | @1 Accounts have been copied. |
SUM435 | Cannot copy from the same subsystem. |
SUM436 | @1 Accounts have been copied. @2 Duplicates have been moved. |
Description: A user ID to be copied already exists in an SCLASS. The user ID was moved to the copy-to SCLASS. | |
SUM437 | Enter the Copy-from subsystem name. |
Description: Copy requires an SCLASS and subsystem name. | |
SUM438 | Enter the Copy-from Sclass name. |
Description: Copy requires an SCLASS and subsystem name. | |
SUM439 | For copy-from fields use one of: Copyuser, CPReplace, or Preview. |
Description: If not copying remove data from copy fields. if copying an invalid PF key was selected. | |
SUM440 | PF KEY or command not available in Browse mode. |
SUM441 | No duplicate Userids were located. |
SUM443 | Field: @1 is not defined in @2. |
SUM444 | BUG.............PAI INTO |
Description: An internal error has occurred while trying to import/export. | |
SUM445 | @1 has already been exported. |
Description: The subsystem must be deleted from D204SYS. If no longer needed use option 9 to delete the subsystem from D204SYS. | |
SUM446 | Unable to import, METADATA/DATALINK entries found for @1. |
Description: There is METADATA or DATALINK information for the specified subsystem to be imported. Delete or rename METADATA/DATALINK information. | |
SUM447 | Cursor not on positioned on a PRIVDEF value. |
Description: To select PF6, the cursor must be placed on a PRIVDEF field for a corresponding file. | |
SUM448 | This account may only update user definitions (PF 9). |
Cross-Reference Facility messages
Number | Message text |
---|---|
XRF001 | Help text not found. Contact System Administrator. |
XRF002 | Error from $BLDPROC. Contact System Administrator. |
XRF003 | Error from $LSTPROC on M204DCTL. Contact System Administrator. |
XRF004 | Unable to find default job procedure: |
XRF005 | Error in Displaying Browsed Procedures |
XRF006 | This PFkey or command is not supported. |
XRF007 | No defined action for ENTER key - please use PFkey or command line. |
XRF008 | XREF Facility is already in use by: |
XRF009 | Procedure file/group required. |
XRF010 | File/Group not open or incorrectly specified. |
XRF011 | Unexpected error from $RDPROC: |
XRF012 | Both ALL and individual report options were selected. |
XRF013 | Global name was not found - procedure cannot be expanded. |
XRF014 | Please specify "N" for Names or "P" for Patterns. |
XRF015 | Please specify at least one Procedure Name or pattern. |
XRF016 | Job Procedure is lacking placeholder: |
XRF017 | Please enter "Y" for Yes or "N" for No. |
XRF018 | Named procedure could not be found: |
XRF019 | Pattern matches no procedure names: |
XRF020 | Number of procedures found: |
XRF021 | WARNING: Modified data will not be stored. Repeat PFkey to |
XRF022 | Global variable name is missing. |
XRF023 | Non-null global variable value is required. |
XRF024 | This global name appears above on this line in your overall list: |
XRF025 | This global name appears below on this line in your overall list: |
XRF026 | BUG - Unable to locate profile record. |
XRF027 | Cannot scroll backwards. |
XRF028 | Cannot scroll forwards. |
XRF029 | More text follows... |
XRF030 | Bottom of text reached |
XRF031 | No help available from here |
XRF032 | Place search string on cmd line and press PF5 or precede with "LOC" |
XRF033 | Search string not located in text below. |
XRF034 | Top of text reached. |
XRF035 | Please use PFkeys instead of ATTN key. |
XRF036 | Request interrupted by ATTN key. |
XRF037 | Record is busy. |
XRF038 | Cross reference job has been submitted. |
XRF039 | The following line has been split for listing purposes. |
XRF040 | Request cancelled. |
XRF041 | File/Group successfully opened. |
XRF042 | Global name contains invalid character in column: |
XRF043 | The specified group has no procfile. |
XRF044 | The specified procedure is currently in use. |
XRF045 | Access to the specified procedure is not allowed. |
XRF046 | Nesting level too deep - maximum allowed is five. |
XRF047 | Command line parameters are incorrectly specified. |
XRF048 | No procedure file or group specified in user profile. |
XRF049 | All globals will be resolved from user profile - GTBL was too small. |
Description: The user might have stored some globals in GTBL immediately before using XREF, but did not leave sufficient free space (1000 bytes) for the XREF facility itself to use. Since GTBL cannot be increased without destroying its contents, GTBL is cleared, and all searches to resolve global dummy strings use the user's profile record. | |
XRF050 | Globals will be resolved from GTBL, then from user profile. |
Description: An informational message: XREF will refer to GTBL during searches to resolve global dummy strings. | |
Messages XRF100-XRF117 | |
Messages XRF100 to XRF117 describe errors detected during Cross Reference facility batch processing.
Messages XRF101 through XRF103 are displayed when the LPP parameter in the job control procedure is invalid or missing. | |
XRF100 | Unable to parse expression - check syntax |
Description: This message is displayed next to statements the parser is unable to recognize. The most common causes of this error are User Language syntax errors and incomplete syntax due to unresolved dummy strings. If you encounter this error for compilable code that does not contain unresolved dummy strings, contact Technical Support. | |
XRF101 | *** WARNING *** ILLEGAL CHARACTERS IN LINES PER PAGE PARM FILE... DEFAULT OF 55 USED |
XRF102 | *** WARNING *** ILLEGAL LINES PER PAGE VALUE... DEFAULT OF 55 USED |
XRF103 | *** WARNING *** LINES PER PAGE PARM FILE EMPTY... DEFAULT OF 55 USED |
XRF106 | IMAGE, ITEM OR ARRAY ITEM NOT DEFINED |
Description: An image, image array or image item contains an AT, AFTER, or DEPENDING ON clause that references another image, array, or item, but the name specified cannot be found in the current image block. This corresponds to Model 204 error message M204.1616. | |
XRF111 | <name> IS AN UNDEFINED STATEMENT LABEL |
XRF112 | <name> IS A MULTIPLY DEFINED STATEMENT LABEL |
XRF113 | <name> IS AN UNDEFINED IMAGE, MENU, SCREEN OR ITEM, OR EXTERNALLY DEFINED COMMON ITEM. |
XRF114 | <name> IS A MULTIPLY DEFINED IMAGE, MENU OR SCREEN |
Last line messages for Technical Support | |
XRF116 | INTERNAL PARSER ERROR. TYPE=xxxx. CONTACT CCA SUPPORT. |
Description: If this message appears in the last line of your CCAPRINT output, contact Technical Support and report the TYPE code. | |
XRF117 | INTERNAL LISTING ERROR. TYPE=xxxx. CONTACT CCA SUPPORT. |
Description: If this message appears in the last line of your CCAPRINT output, check for incorrect input in:
//CCAPROCI DD * Edit the XREF job while in the XREF subsystem (PF4=EDItjob) and ensure that the first lines in the XREF step are exactly these and nothing else: //XREF EXEC PGM=M204XREF //CCAPROCI DD * //*M204XREF /* Then resubmit the job. If the error reappears, contact Technical Support and report the TYPE code. |