CASXB0040S The input file is not a valid MF Forms .frm file The input file has an .frm (upper or lowercase) extension, but is not a valid Micro Focus Forms file. Some compatibility
exists for migrating Micro Focus Forms files into this screen painter's native format, though some incompatibility does exist.
CASXB0043S The input file is not a valid MF Screens .srn file The input file has an .srn (upper or lowercase) extension, but is not a valid Micro Focus Screens file. Some compatibility
exists for migrating Micro Focus Screens files into this screen painter's native format, though some incompatibility does
exist.
CASXB0046I No DFHMDI SIZE arg. Using configured default map size This map does not have an explicit SIZE parameter, which will cause it to be displayed differently on different display sizes.
In order to render the map in the painter, the painter's default map size (configurable) is arbitrarily used. Note that any
fields must be expressed as POS=offset instead of POS=(row,col). When regenerating BMS from the painter, if a map size is
not specified, the generated field macros will be expressed as POS=nnnn instead of POS=(row,col).
CASXB0049W CTRL ignored... Already specified in DFHMSD macro The CTRL parameter was already specified in the DFHMSD macro. Contrary to the CICS 3.3 Applications Programming Reference
Manual, and contrary to normal inheritance rules, this value does not supersede the mapset specification.
CASXB0050W ATTRB=IC specified for a protected field. Accepted. A protected field (ASKIP or PROT) wouldn't normally have the cursor placed in it, though it is allowed, since the application
may dynamically change the field to unprotected before the map is sent.
CASXB0051E Repeated fields must have same LENGTH, PICIN and PICOUT Repeated field (array) instances must yield compatible dsect definitions in order to be rendered into an array. Although some
properties can differ, the LENGTH, PICIN and PICOUT values must be identical. The repeated field instance was detected by
finding that the previous named field had the same alternate-name in its comment (SDF-mode or ADVS-mode only).
CASXB0054W Input performance is improved with fields in ascending sequence Runtime performance is improved when fields are defined in sequence (ascending position), though this is not required. However,
arrays, groups and other dsect structures may prevent fields from being defined in pure ascending sequence.
CASXB0055W Field runs beyond end of defined map size. The field's position and length will cause it to extend beyond the defined (or implied) map dimensions. At runtime, if the
map size equals the screen size, the field will wrap round to the beginning of the map. If the map size is smaller than the
screen size, the field will extend beyond the end of the map. This can cause unpredictable results rendering user input at
runtime.
CASXB0056W Comment-card continued. Contents of next line ignored. A comment card contained a non-blank character in column 72, indicating it is to be continued. This is syntactically correct,
but may indicate a typographical error, and can cause the next macro to be accidentally ignored.
CASXB0059I Loading as an MF <product> type file The input file extension is causing the file to be read as a <product> (Forms, Forms2, Screens) file. This informational message can help clarify if a file does not appear to be loading properly.