Micro Focus Enterprise Developer 2.3 for Eclipse
>
Programming
>
Mainframe Programming
>
AppMaster Builder
>
Reference
>
Error Messages
>
PTR- Painter system messages
PTR- Painter system messages
Restriction:
This topic applies only when the AppMaster Builder AddPack has been installed, and applies only to Windows platforms.
Select the number of the message you require details about:
PTR -5410-00-E COPY only allowed with 01 TYPE keyword
Use the COPY verb only with an 01 keyword for data structures.
PTR -5415-00-E Multiple PROC keywords are invalid
PTR -5424-00-E Line can only start with $ & - or alpha character
Line must start with valid alpha COBOL character or Customizer symbol ($ % & or /).
PTR -5425-00-E No room for a closing period on this line
Line in program is too long for period to be added during conversion.
PTR -5428-00-E ENTER verb must be followed by COBOL or S-COBOL only
A statement beginning with ENTER has a word other than COBOL or S-COBOL after it.
PTR-0000-00-I Copyright year MICRO FOCUS &sq&APS-rel &pgm-id &compiletime&sq
PTR-0201-00-I EXP-0201-00-I Data structure change successful
This message occurs when using the K line call, and all changes or line additions are correct when passed back to the Program Painter.
PTR-0204-00-I Convert not successful
An error was encountered in the code. Correct error before continuing.
PTR-0400-00-I Only keyword needed is REC - keyword changed
If keywords such as WS or CA are entered, the Data Structure Editor no longer requires them and converts them to REC.
PTR-0800-00-I Info-literal may not be contained within QUOTES-APOSTS
The TRANCODE literal field was entered with quotes. The quotes were removed because they are not valid.
PTR-0801-00-I INFO-FILL character of NULL assumed for PFKEY
The TRANCODE Fill field was changed to N since TRANCODE is a PF key and not a literal.
PTR-1801-00-W xmlPFKEY specified as trancode but not defined PFKEY trancode ignored
*PFkey was supplied in the trancode construction dialog box, but no values were assigned the MFS function keys.
PTR-1805-00-W Warning - Field name SYSMSG conflicts with SYSMSG parm value
"SYSMSG" was used as the name for an IO field, and "YES" or "SYSMSG" was specified in the SYSMSG field.
PTR-1806-00-W Warning - SYSMSG over AMB text repeated block or I-O field
SYSMSG or YES was specified in the SYSMSG field, but the default line for building the SYSMSG field already contains a field on it.
PTR-1807-00-W Warning - Oper logical paging requested without trancode field
Operator logical paging was set to YES, but an optional trancode field name or trancode construction was not specified. See Assigning Screen Attributes.
PTR-1809-00-W Warning - TC constructed but xmlTC not specified for trancode fld
Field names or default literals were supplied for trancode construction screen, but trancode construction was not activated.
PTR-1810-00-W Warning - PFKEYS defined but xmlPF not specified for trancode fld
PFkey values were supplied for the MFS function keys, but the function keys weren't activated as the trancode.
PTR-5401-00-E Format on group level is not allowed
Format is entered next to a group level. This is illegal in COBOL.
PTR-5422-00-E No match for quote or apostrophe
Arguments have incorrect syntax. Ensure that each quote or apostrophe is paired.
PTR-5432-00-E PARA keyword must be followed by a paragraph name or section name in column 8 on the same line as the PARA keyword
PTR-5433-00-E Literal exceeds 120 characters
Continuation of a literal exceeds 120 characters. The literal is too long.
PTR-5435-00-E Above keyword must be followed by the entity name to be accessed
The required entity name missing after the keyword.
PTR-5436-00-E The above keyword is invalid
PTR-5800-00-E Error-literal contains illegal characters - line
The literal contains quotes. Remove the quotes from the literal.
PTR-5802-00-E Error - xmlPFKEY may only be specified once per trancode
The transaction code cannot be built using repeated names.
PTR-5803-00-E Error - fld name may not be used twice in trancode - line
Cannot construct trancode using a field more than once.
PTR-5809-00-E Error - row specified for SYSMSG not numeric or out of range
The line number specified for SYSMSG is less than 1 or greater than screen depth.
PTR-5810-00-E Error - invalid characters contained in field
A character was found that was not alphabetic, numeric, or '#', '$', or '@'.
PTR-5811-00-E Error - DIF-DOF-MID-MOD names must be unique
The input and output maps can't be distinguished from each other.
PTR-5812-00-E Error - segment exit not numeric or out of range
The MID segment exit number or vector is not numeric or is out of range.
PTR-5813-00-E Error - both nbr and vector are required for segment exits
The MID segment exit number and vector are not compatible.
PTR-5814-00-E Error - value specified for MOD fill character is invalid
Fill character can only be null. Enter 'NULL' in field.
PTR-5815-00-E Error - intensity may only be BRIGHT or NORMAL for text
PTR-5816-00-E Error - invalid value specified for COLOR
Abbreviation entered for color selection is invalid.
PTR-5818-00-E Error - numeric range specified is invalid
Either the ranges specified exceed the screen size, or the first range exceeds the second range. See numeric range.
PTR-5819-00-E Error - length specified for SYSMSG not numeric or out of range
The length specified for SYSMSG not numeric, or it exceeds the screen width.
PTR-7400-00-E Invalid keyword in indicated line
Keyword entered is not recognized by the Painter system.
PTR-7401-00-E 77 level must start in margin A
A 77-level data item must start in column 8.
PTR-7402-00-E Data name must start with alpha or &
Data names must begin with an alphabetic character, & or < .
PTR-7403-00-E Level will be too high -- highest level is 49
A level higher than 49 will be generated.
PTR-7404-00-E Invalid syntax after data name
Syntax violates COBOL or Data Structure call syntax.
PTR-7406-00-E Only data name can follow 88 or 66 levels
A valid data name must follow an 88 or 66 . . . RENAMES level number.
PTR-7407-00-E Data name for structure must be on line 1
All data structures must have a valid keyword and data name on line 1.
PTR-7408-00-E Alphabetic format AAAAAAANA(N) A(&SYM)
If an A is the first character in the format field, then the code must be in one of the valid formats.
PTR-7409-00-E Invalid computational (C) form at spec
C is invalid as used. Use a valid format.
PTR-7412-00-E Numeric format NN2N3N$ NKN(K)N&SYM
If an N is the first character in the format field, then the code must be in one of the valid formats.
PTR-7413-00-ERedefines format is R RED REDEF REDEFINES
Invalid format for REDEFINES was entered.
PTR-7414-00-E Signed numeric format S SN S&SYM
Signed symbol is invalid format as used.
PTR-7415-00-E Alphanumeric format XXXXXXXKX(K)X(&SYM)
Alphanumeric symbol is invalid format as used.
PTR-7416-00-E Numeric format 99293949K9(K)9&SYM
Numeric format is invalid format as used.
PTR-7417-00-E To indicate PICTURE must use PIC
If the P is the first character in the format field, then the PICTURE clause is expected.
PTR-7418-00-E OCCURS specification not allowed in format
OCCURS symbol is not entered in the data name field.
PTR-7422-00-E Invalid character follows space in format
Only V or R can continue a format.
PTR-7423-00-E Value can be first format only on 88 levels
Only an 88 level value can be assigned first in a format.
PTR-7424-00-E Invalid data format Recheck format specification
This is an invalid data structure.
PTR-7425-00-E Cannot specify format for a group level item
A PICture clause on a group level is illegal.
PTR-7428-00-E No format spec allowed on 66 level RENAMES
Invalid format on 66-level data item.
PTR-7429-00-E V (VALUE) is only valid format for 88 levels
Invalid 88-level data items format.
PTR-7430-00-E Selected entity is being edited by another
PTR-7431-00-E No spaces allowed in FMP variable name
The variable name has space(s) embedded in it.
PTR-7432-00-E Comments start in data name field - no keyword
Comment line was specified in the keyword field.
PTR-7480-00-E Valid formats beginning with I are I or INDEXED
PTR-7481-00-E Valid formats beginning with R are R or REDEFINES
PTR-7483-00-E PICTURE clause incomplete--no data field type specified
An empty PIC clause was entered. Enter a valid PICture clause.
PTR-7484-00-E OCCURS clause is described with invalid occurrence of table
An invalid statement following the OCCURS clause was entered.
PTR-7485-00-E REDEFINES clause must precede OCCURS clause
The OCCURS specification must be entered before the REDEFINES clause.
PTR-7490-00-E EGCS value too long
The EGCS literal exceeds 54 characters, the limit for EGCS literals.
Parent topic:
Error Messages
