Rule compilation errors

This chapter lists the Rule compilation errors and, when it exists, any additional information needed to deal with the problem.

Rule compilation error messages

04003 The O.E. descriptor file is empty

  • Type: User
  • Cause: The Output segment descriptor file must contain at least one Output Segment structure, otherwise AccountingIntegrator cannot manage the rules.
  • Action: You need to create an Output Segment descriptor.

 

04004 Doesn’t exist

  • Type: User
  • Cause: The table key allowing the search for a value in the table (which Rule Manager needs) is not present in the table file.
  • Action: Add the missing table key to the table concerned or modify the mapping rule calling this table key.

 

04005 THE WORKSTATION/HOST CODE IS INCORRECT

  • Type: User
  • Cause: This is a batch entry error. The local code / host for a rule, scenario or mapping rule differs from the following values: L, C, LC.
  • Action: The error zone is the local /host code, you need to enter the following values: L, C, LC.

 

04006 AN ERROR OCCURRED WHEN THE COMPILER WAS INITIALIZED

  • Type: Error
  • Cause: The parameter file used is not up to date; for example, we mention the case of the rule code which would be located at position "10" in the parameter file, while in the Input Event it would be located at position "1".
  • Action: There are two courses of action:
    • The administrator modifies the parameter file
    • The user modifies the zone positioning in the Input Event or Output Segment

 

04007 THE COMPILER STACKS ARE OUT OF PHASE

  • Type: Error
  • Cause: The compiled rules file is not reliable. Please call the hot line.
  • Action: You need to create an Output Segment descriptor.

 

04009 THE O.E. STRUCTURE HAS ONLY A HEADER

  • Type: User
  • Cause: Batch entry error, an Output Segment descriptor should contain at least one Output Segment field.
  • Action: You need to enter at least one field into the Output Segment descriptor, also known as structure.

 

04010 AN ERROR OCCURRED IN THE O.E. STRUCTURE FILE

  • Type: Error
  • Cause: The Compilation process detected an error during the Output Segment descriptor check. The process stops.
  • Action: The error must be corrected, assistance is provided from the error messages output by the compilation process. Then restart compilation.

 

04011 THE O.E. STRUCTURE HEADER IS MISSING

  • Type: Error
  • Cause: This is either a batch entry error (the record containing the global information for an Output segment is not present) or the DESCEE file secondary key is badly defined.
  • Action: The correction must be made to the first symbolic field name you come across or to the redefinition of the DESCEE file at JCL level.

 

04012 THE O.E. STRUCTURE IS LONGER THAN THE MAXIMUM PERMITTED

  • Type: User
  • Cause: 2 possibilities:
    • The maximum length of the Output segments (contained in the parameter files) has been modified since the Output segment descriptors were entered, creating an inconsistency.
    • Batch entry error. Check the length defined for this Output segment in the record header.
  • Action: There are two possible solutions:
    • Modify parameters in the Optimization section in the functional context file
    • Reduce the length of the Output segment concerned

 

04013 THE START POSITION IS NOT NUMERIC

  • Type: User
  • Cause: Batch entry error. The elementary field start position for the Output or Input Segment must be numeric (mandatory) and greater than zero.
  • Action: Modify the field positioning concerned in the elementary script.

 

04014 THE LENGTH IS NOT NUMERIC

  • Type: User
  • Cause: Batch entry error. The length of the elementary field for the Output or Input Segment must be numeric (mandatory) and greater than zero.
  • Action: Check the length of the Output segment zone concerned.

 

04015 POSITION + THE LENGTH IS GREATER THAN MAXLG

  • Type: User
  • Cause: Batch entry error. The length of the elementary field is such that it exceeds the Input or Output segment.
  • Action: Check the length of the Output segment (contained in the header) or the length of the Input Segment (contained in the parameter file) and also the position and length of the elementary field. Error localization: Maximum length of Input or Output segment.

 

04016 THE DATA TYPE IS INCORRECT

  • Type: User
  • Cause: Batch entry error.
  • The data type of an elementary field must be (mandatory):
    • A (alphanumeric)
    • N (numeric)
    • D (date)
    • P (packed)
    • S (signed)

 

04017 THE LENGTH AND DATA TYPE ARE INCOMPATIBLE

  • Type: User
  • Cause: Batch entry error. Depending on the elementary field data type, its length must be less than or equal to a maximum length of the following:
    • Data type = A Maximum length = 256
    • Data type = N, P, S Maximum length = 18
    • Data type = D Length = 6 or 7
  • Action: Check the length of the field concerned compared with its data type.

 

04018 THIS FIELD NAME IS PROHIBITED

  • Type: User
  • Cause: Batch entry error. The symbolic field name used in the definition of an Output or Input Event structure is a word reserved by the Interpreter system (the reserved words are in the "MOTRES" table in the Parameter file).
  • Action: Modify the symbolic field name used.

 

04019 THE O.E. MAPPING RULE IS MISSING

  • Type: User
  • Cause: A rule version must have at least one Output segment mapping rule order.

 

04020 TWO VERSIONS OVERLAP, END DATE OF THE PREVIOUS VERSION:

  • Type: User
  • Cause: The validity period start date for a rule version must be later than the expiry date of the previous version.
  • Error localization: Expiry date for the previous version.
  • Action: Check the 2 rules concerned and change their validity period dates.

 

04021 AN ERROR OCCURRED WHEN THE VERSION WAS SET

  • Type: Error
  • Description: Rules for compilation not found.

 

04023 THERE ARE TOO MANY VERSIONS FOR THE RULE

  • Type: Error
  • Description: The maximum number of versions for a given rule is 50, above this limit the rule is stated to be in error.
  • Action: Delete the versions that are no longer in use.

 

04024 THE OCCURRENCE MANAGEMENT DEFINITION IS INCOMPLETE

  • Type: User
  • Comment: Specify the number of incidents.

 

04025 THE ".." COMMANDS ARE USED AT THE WRONG TIME

  • Type: User
  • Comment: When an Input Event is enriched, it is not possible to use the commands

 

04026 THE ".." COMMANDS USED ARE INCOMPATIBLE

Type: User

 

04027 COMMAND ".." IS NOT RECOGNIZED - (UNKNOWN)

Type: User

 

04028 THE ".." COMMANDS USED ARE CONCATENATED INCORRECTLY

Type: User

 

04029 AN ERROR OCCURRED WHEN THE RULE WAS SET

  • Type: Error
  • Cause: The uncompiled rule description file (RGCLIN) is empty.

 

04030 THE PRINT POSITION IS INVALID(<> 0060 TO 0132, 0000, 9998, 9999)

  • Type: User
  • Cause: Invalid print position.
  • Action: The print position for a symbolic field name on the accounting journal may be equal to "0". In this case this journal is not printed, otherwise the print position must be between "60" and "132".

 

04031 THE PRINT DETAIL CODE IS INVALID

  • Type: User
  • Action: The print detail code is not valid, permitted values are:
    • Y (yes)
    • N (no)

 

04032 THE STRUCTURE HAS MORE THAN 20 PRINT POSITIONS

  • Type: User
  • Cause: the selection to print the accounting journal includes more than 20 zones, but AccountingIntegrator allows a maximum of 20 zones.
  • Action: Reduce the number of zones to print on the accounting journal to a maximum of 20.

 

04033 THERE ARE MORE THAN 80 I.E. CHARACTERS TO SORT

  • Type: User
  • Cause: When the aggregation function is activated the sort function is carried on 80 characters maximum only.
  • Action: You need to revise the sort criteria so that they are restricted to 80 characters at the most.

 

04034 THERE ARE MORE THAN 80 I.E. ZONES TO SORT

  • Type: User
  • Cause: When the aggregation function is active, the sort criteria limit is 100 Input Zones maximum.
  • Action: You need to reduce the number of zones used for the sort function to ensure there are no more than 100.

 

04035 THERE ARE MORE THAN 50 I.E. ZONES TO AGGREGATE

  • Type: User
  • Cause: Where the aggregation option is active, there are more than 50 zones to aggregate, but the Rule Manager has a maximum limit of 50 zones.
  • Action: You need to reduce the number of zones to aggregate to ensure there are no more than 50.

 

04036 THE SORT CODE ALREADY EXISTS

  • Type: User
  • Cause: Where the aggregation option is active, there is already an Input Event symbolic field name which has this sort code (possible values are 01 to 99, 00 = no sort).
  • Action: Check the sort code values, 2 symbolic field names in the Input Event have the same sort code.

 

04037 TRANSFER BETWEEN THESE TWO DATA TYPES IS PROHIBITED

  • Type: User
  • Cause: Transfer between 2 zones is not permitted because the 2 data types are not compatible, for example it is not possible to transfer from packed to alphanumeric.
  • Action: Identify the problem and revise the field descriptions.

 

04038 SORT ZONES WITHOUT ZONES TO AGGREGATE (OR VICE-VERSA) FOR I.E.

  • Type: User
  • Cause: The aggregation option is active and the sort zones or aggregation zones have not been specified.
  • Action: In the Input Event set up the sort zones or the zones for aggregation if the user wishes to aggregate.

 

04039 TRANSFER BETWEEN THESE TWO DATA TYPES IS NOT RECOMMENDED

Type: User

 

04040 THE TRANSFER INVOLVES A RISK OF TRUNCATION

Type: User

Comment: The receiving zone is smaller than the sending zone.

 

04041 THE END DATE IS EARLIER THAN THE START DATE

Type: User

Description: The end date is earlier than the start date.

Action: Modify the dates so that the start date is before the end date.

 

04042 TRANSFER TO A FIELD CONSIDERED TO BE A DATE

  • Type: User
  • Cause: The Output segment descriptor file must contain at least one Output Segment structure, otherwise AccountingIntegrator cannot manage the rules.
  • Action: You need to create an Output Segment descriptor.

 

04043 THERE ARE MORE THAN 256 O.E. CHARACTERS TO SORT

  • Type: User
  • Cause: When the aggregation function is active, the sort function is carried on 256 characters maximum only.
  • Action: You need to revise the sort criteria so that they are restricted to 256 characters at the most.

 

04044 THERE ARE MORE THAN 80 O.E. ZONES TO SORT

  • Type: User
  • Cause: When the aggregation function is active, the sort criteria limit is 100 Input Zones maximum.
  • Action: You need to reduce the number of zones used for the sort function to ensure there are no more than 100.

 

04045 THERE ARE MORE THAN 50 O.E. ZONES TO AGGREGATE

  • Type: User
  • Cause: Where the aggregation option is active, there are more than 50 zones to aggregate, but the Rule Manager has a maximum limit of 50 zones.
  • Action: You need to reduce the number of zones to aggregate to ensure there are no more than 50.

 

04046 THE SORT CODE ALREADY EXISTS

  • Type: User
  • Cause: Where the aggregation option is active, there is already an Input Event symbolic field name which has this sort code (possible values are 01 to 99, 00 = no sort).
  • Action: Check the sort code values, 2 symbolic field names in the Input Event have the same sort code.

 

04047 COMPARAISON WITH TOO LONG A CONSTANT

Type: User

 

04048 SORT ZONES WITHOUT ZONES TO AGGREGATE (OR VICE VERSA) FOR O.E.

  • Type: User
  • Cause: The aggregation option is active and the sort zones or aggregation zones have not been specified.
  • Action: In the Input Event set up the sort zones or the zones for aggregation if the user wishes to aggregate.

 

04049 CONCATENATION EXCEEDS 256 CHARACTERS

Type: User

 

04050 THERE ARE TOO MANY DESCRIPTIONS FOR THE I.E.

Type: User

Comment: The description of the Input Event exceeds the limit of 500 fields.

 

04051 THE I.E. DESCRIPTOR DOES NOT EXIST

  • Type: User
  • Cause: The rule version being checked does not include the Input Event descriptor.
  • Action: An Input Event description should be linked with this rule version.

 

04052 THE SEQUENCE NUMBER IS TOO HIGH OR NOT NUMERIC

  • Type: User
  • Cause: Batch entry error.
  • The mapping rule order number is not numeric or is equal to zero or is higher than the permitted limit (50).
  • Action: Modify the mapping order sequence number so that it is numeric and between "1" and "50".

 

04053 THE O.E. STRUCTURE IS UNKNOWN

  • Type: User
  • Cause: The Output segment structure assigned to the mapping rule does not correspond to any structure that exists in the Output segment descriptor file.
  • Action: There are 2 options:
    • Check that the Output segment structure has not been deleted in error from the Output segment file
    • Correct the structure in the mapping rule order

 

04054 THE FIELD NAME DOES NOT EXIST IN THE I.E.

Type: User

Comment: A symbolic field name used in the Output segment mapping rules has not been defined in the Input Event structure.

 

04055 THE STRUCTURE CODE IS INCOMPATIBLE WITH THE HEADER

  • Type: User
  • Cause: Batch entry error.
  • The local/host code for the elementary field of a mapping rule is not the same as that in the mapping rule header.
  • Action: The local/host code must be "L", "C" or "LC"; anything other than these values produces an error output.

 

04056 ONLY A HEADER

  • Type: User
  • Cause: The designated Output segment mapping rule does not contain symbolic field names.
  • Action: An Output segment mapping rule must contain at least one symbolic field name.

 

04057 THE FIELD NAME DOES NOT EXIST IN THE O.E. STRUCTURE

  • Type: User
  • Cause: You deleted by mistake a field used in a mapping rule from the Output segment structure.
  • Action: If the user wishes to delete a field from a structure, it is necessary first to remove the mapping rules where it is located. In this case you must add the missing field to the structure before doing anything else.

 

04058 THE MANDATORY FIELD NAME IS MISSING FROM THE MAPPING RULE

  • Type: User
  • Cause: No mapping rule for a field that you had declared as mandatory in your structure.
  • Action: There are 2 solutions:
    • Do not make the zone mandatory in the structure
    • Set up a mapping rule for the zone in question

 

04059 THERE IS NO SCENARIO FOR THIS RULE VERSION

  • Type: User
  • Cause: A rule version must have at least one scenario.
  • Action: You need to create an execution scenario for this rule version.

 

04060 THE DATE COMPARAISON HAS DIFFERENT DATA TYPES

Type: User

 

04061 THE SEQUENCE DOES NOT EXIST

  • Type: User
  • Cause: A sequence described in the scenario sequence table has not been defined or has been deleted.
  • Action: In the first case, supply a definition, in the second, modify the scenario.

 

04062 THE SCENARIO NUMBER IS TOO HIGH OR NOT NUMERIC

  • Type: User
  • Cause: The scenario number must be numeric and less than or equal to the maximum value set in the parameter file.
  • Action: The maximum number of permitted scenarios is "10", but it is possible to limit this in the parameter file. The value in the parameter file needs to be verified.

 

04063 THE SEQUENCE TABLE IS LOADED INCORRECTLY

  • Type: User
  • Cause: Batch entry error. The table or sequences of a scenario has a "00" between two field numbers to be mapped.
  • Action: The Input Form needs to be corrected.

 

04064 DOUBLE SEQUENCE

  • Type: User
  • Cause: Batch entry error. The same sequence is occurring at least twice in the scenario sequence table.
  • Action: Modify the Input Form.

 

04065 THERE IS NO SEQUENCE FOR THE SCENARIO

  • Type: User
  • Cause: A scenario should have at least one sequence.
  • Action: At least one Output Segment should be linked to a scenario.

 

04066 WORKSTATION/HOST CODE INCOMPATIBILITY BETWEEN SCENARIO AND RULE

  • Type: User
  • Cause: The local/host code for the scenario is not compatible with that defined for the rule version.
  • Action: Error localization:
    • Local/host code for the version
    • Local code/host for the scenario

 

04067 WORKSTATION/HOST CODE INCOMPATIBILITY BETWEEN THE O.E. AND RULE

  • Type: User
  • Cause: The local/host code for the Output segment mapping rule is not compatible with that of the scenario.
  • Action: Error localization:
    • Local code/host for the scenario
    • Number of the sequence concerned
    • Local/host code for the sequence

 

04068 NO O.E. CORRESPONDING TO THE SCENARIO WORKSTATION/HOST CODE

  • Type: User
  • Cause: There should be at least one mapping rule order corresponding with the scenario local/host code.
  • Action: If the code is LC, mapping rules are required either with a code LC or there should be at least one mapping rule with code L and one mapping rule with code C.
  • Error localization: Local/host code for the scenario.

 

04069 NO SCENARIO CORRESPONDING TO THE RULE WORKSTATION/HOST CODE

  • Type: User
  • Cause: There should be at least one scenario corresponding to the rule local/host code.
  • Action: If the code is LC, scenarios are required either with a code LC or there should be at least one scenario with code L and one scenario with code C.
  • Error localization: Local/host code for the rule.

 

04070 WORKSTATION/HOST CODE INCOMPATIBILITY BETWEEN PARAMETER AND RULE

Type: User

 

04071 THE SCENARIO CONDITION MUST NOT BE USED TO MODIFY THE I.E.

  • Type: User
  • Comment: For an Input Event enrichment rule, with no Output segment production, the scenario must not be conditioned and must have in its list an Output segment numbered 99.

 

04072 THE I.E. MODIFICATION MAPPING RULE IS MISSING

Type: User

 

04073 TRANSFER OF TOO LONG A CONSTANT

Type: User

 

04074 A NUMERIC TRANSFER FROM TOO LONG A ZONE

Type: User

 

04075 THE OPERAND IS NOT VALID FOR THE OPERATION CODE:

Type: User

 

04076 INCORRECT USE OF "LOW-VALUE" OR "HIGH-VALUE"

Type: User

 

04077 TRANSFER FROM WORKING ZONE LEVEL > 1

  • Type: Error
  • Comment: Serious error at compiler level. Contact Axway support.

 

04079 THE RGTR FILE WAS CREATED INCORRECTLY - THE SUFFIX IS INCORRECT

Type: Error

 

04080 AN ERROR OCCURRED IN THE LEXICOGRAPHIC ANALYZER

  • Type: User
  • Cause: An error was detected during the lexicographic analysis at scenario condition level or at Output segment field mapping rule level.
  • Action: Modify the field concerned.

 

04090 AN ERROR OCCURRED IN THE SYNTACTIC ANALYZER

  • Type: User
  • Cause: An error was detected during the syntactical analysis in the scenario condition or elementary field mapping rule condition.
  • Action: Modify the field concerned.

 

04091 DOESN’T EXIST

  • Type: User
  • Cause: A loading error has occurred in the “RGTR” file.

 

04096 AN ERROR OCCURRED WHEN THE SYNTACTIC ANALYZER WAS INITIALIZED

Type: Error

 

04098 AN ERROR OCCURRED WHEN THE LEXICOGR. ANALYZER WAS INITIALIZED

Type: Error

 

04099 THE PROGRAM DOES NOT PROVIDE FOR THIS CASE

  • Type: Error
  • Cause: Write error in the "RGTR" compiled rules file. The disk is full or the file is damaged.

 

04100 COMPARISON BETWEEN A DATE AND A CONSTANT WITH 6 CHAR.

Type: User

 

04101 COMPARISON BETWEEN A DATE AND A FIELD WITH LENGTH # 6,7,8

Type: User

 

04102 COMPARISON INVOLVING PROBABLY A "HIDDEN" DATE

Type: User

 

04105 TRANSFER OF A DATE INDUCING A CONVERTION

Type: User

 

04106 TRANSFER TOWARDS A DATE FROM A FIELD WITH LENGTH # 6,7,8

Type: User

 

04107 TRANSFER INVOLVING PROBABLY A "HIDDEN" DATE

Type: User

 

04500 ERROR WHEN LOADING THE PARAMETERS TABLES FOR LEXICO. ANALYZER

  • Type: Error
  • Cause: The tables in the parameters file used in the lexicographic analysis are not complete.
  • Action: Check the parameter file.

 

04505 THE CONSTANT IS EMPTY

  • Type: Error
  • Cause: The lexicographic analyzer has found a field specified as "constant" to be empty.
  • Action: Check the field concerned.

 

04506 THE CONSTANT IS NOT NUMERIC

Type: Error

 

04507 THE CONSTANT ZONE IS FULL

  • Type: User
  • Cause
    • A field in which the user wishes to place a constant signaled by ("..") should contain a maximum of:
      • 18 characters if it is specified as numeric
      • 256 characters if it is specified as alpha-numeric
      • In this case, the maximum value has been exceeded.
    • The constants of a mapping rule consist of:
      • All the constant fields that are different from one another
      • All the table names that are different from one another
      • The total of these characters for mapping the entire elementary script must not exceed 256 characters.

 

04508 THE CONSTANT IS NOT COMPLIANT

Type: User

 

04509 CONSTANT "19": USAGE TO BE CHECKED (Y2K)

Type: User

 

04510 THE PILEAL MEMORY ZONE IS TOO SMALL (LEXICOGRAPHIC ANALYZER)

  • Type: Error
  • Cause: The stacking memory zone is too small (lexicographic analyzer). In other words the expression is too complex (too many parenthesis levels).
  • Action: Simplify the expression in question.

 

04511 NUMBER "(" IS DIFFERENT FROM NUMBER ")"

  • Type: User
  • Cause: The number of opening parentheses differs from the number of closing parentheses.
  • Action: The number of opening parentheses must be the same as the number of closing parentheses.

 

04515 THE ZONE OVERFLOWED DURING AN END OF CONSTANT SEARCH

  • Type: User
  • Cause: The character indicating the end of the constant is missing.
  • Action: Add the character indicating the end of the constant: ( " ).

 

04520 THE CONSTANT IS NOT DELIMITED

  • Type: User
  • Cause: A field in which the user wishes to place a constant signaled by ("..") should contain a maximum of:
    • 18 characters if it is specified as numeric
    • 256 characters if it is specified as alpha-numeric
  • In this case the maximum value has been exceeded or the maximum character to indicate the end of the constant is missing.
  • Action: Set up a constant for the field in question.

 

04521 THE NUMERIC CONSTANT IS TOO LONG (> 18 CHAR)

Type: User

 

04522 ZONE OVERFLOW DURING A SEPARATOR SEARCH

  • Type: Error
  • Cause: A separator is missing from the mapping rule expression.

 

04525 THE MAXIMUM NUMBER OF CHARACTERS (10) FOR A WORD WAS EXCEEDED

  • Type: User
  • Cause: A word signifying the expression of condition or mapping rule (after the type of processing code) is longer than the 10 characters allowed.
  • Action: The word is too long, reduce it to 10 characters maximum.

 

04529 THE TABLE NAME IS UNKNOWN

Type: User

 

04530 THE WORD DOES NOT FIT ANY CATEGORY (I.E.,SEPARATOR,OPERATOR,...)

  • Type: User
  • Cause: The word does not come under any category (separator, operator, Input Event…)
  • Action: It is essential that the word be: either an operator or an operand.

 

04531 REFERENCE WAS MADE TO AN UNMAPPED O.E. ZONE

Type: User

 

04532 REFERENCE TO AN UNKNOWN O.E. ZONE

Type: User

 

04533 THE OPERAND IS INCORRECT

Type: User

 

04534 THE TRANSFER CODE IS INCORRECT

  • Type: Error
  • Cause: Contact Axway support.

 

04535 ERROR WHEN LOADING THE PARAMETERS TABLES FOR THE RULE COMPILER

Type: Error

 

04536 THE MAPPING RULE IS TOO COMPLEX --> SIMPLIFY

Type: Error

 

04537 THE MAPPING RULE FOR THIS FIELD IS ALREADY CODED

Type: Error

 

04538 REFERENCE TO AN UNKNOWN VARIABLE ZONE

Type: User

 

04539 THE MAPPING RULE IS OVERLOADED --> PARENTHESIZE INTO SUB-GROUPS

Type: Error

 

04540 THE OCCURRENCE MAPPING IS TOO COMPLEX --> SIMPLIFY

Type: Error

 

04600 PARENTHESES ARE MISSING OR THE EXPRESSION IS TOO COMPLEX

  • Type: User
  • Cause: The expression is too complex, or a parenthesis is missing.
  • Action: If parentheses are added, the lexicographic analyzer can perform the analysis more efficiently.

 

04601 AN ERROR OCCURRED IN THE SYNTACTIC ANALYZER

  • Type: User
  • Cause: Error in the syntactic analyzer.

 

04602 ERROR WHEN LOADING THE PARAMETERS TABLES FOR SYNTAC. ANALYZER

  • Type: Error
  • Cause: The table in the parameter file is not complete.
  • Action: Check the tables in the parameter file and complete the table concerned.

 

04603 NUMBER ")" IS GREATER THAN NUMBER "("

  • Type: User
  • Cause: There are more closing parentheses than opening parentheses.
  • Action: The number of opening parentheses must be the same as the number of closing parentheses.

 

04605 THE ";" OPERATOR IS INVALID

  • Type: User
  • Cause: Invalid operator
  • The ";" character is used only for the following functions:
    • $NBDAYS
    • $CHECKTABD
    • $ACCTABD
    • $EXTTABD
  • It may not be used anywhere else.
  • Action Remove the ";" character.

 

04606 THE "THEN" SYMBOL IS MISSING OR NO ACTUAL CONDITION EXISTS

  • Type: User
  • Cause: A conditional expression must always contain a "THEN" between the condition and the expression to be executed if the condition is true.
  • Action: Add the missing expression.

 

04607 THE PARENTHESES ARE MISSING FROM AN AND/OR CONDITION

Type: User

 

04608 NUMERIC SIMULATION IS NOT POSSIBLE FOR THIS FIELD

Type: User

 

04609 THE OPERATOR CODE IS UNKNOWN

  • Type: Error
  • Cause: Incompatibility between the operator tables (TCDOP and OPERAT) in the parameter file.
  • Action: Contact Axway support.

 

04610 THE FOLLOWING SYMBOLS MUST NOT BE CONSECUTIVE

Type: User

Cause: Syntax error in the condition or mapping rule script ; the symbols quoted must not be consecutive.

Action: Separate the symbols concerned.

 

04611 THE OPERAND DATA TYPE IS INCOMPATIBLE WITH THE NEXT OPERATOR

  • Type: User
  • Cause: The operator quoted may not be preceded by an operand of this type.

 

04612 THE OPERAND DATA TYPE IS INCOMPATIBLE WITH THE PREVIOUS OPERATOR

  • Type: User
  • Cause: The operator quoted may not be preceded by an operand of this type.

 

04613 THE CONDITIONAL EXPRESSION IS INCOMPLETE

  • Type: User
  • Cause: The expression of mapping rule condition contains a "THEN" symbol but does not contain an "IF". The condition expression contains two consecutive "THEN" symbols or an "ELSE" followed by a "THEN".
  • Action: Redraft the condition expression as follows:
  • "IF" "THEN" "ELSE"

 

04614 THE "IF" OPERATOR IS USED OUT OF CONTEXT

  • Type: User
  • Cause: the "IF" operator is used out of context
  • Action: The "IF" operator may not be used except in the mapping rule for an Output segment field. It must be the first operator, or immediately follow an "ELSE".

 

04615 THE BEGINNING OF THE (IF...THEN ...) EXPRESSION IS MISSING

  • Type: Error
  • Cause: Serious problem in calling the lexicographic analyzer.

 

04703 SEARCH: THE FIRST PARAMETER IS INVALID

Type: User

 

04704 SEARCH: FIRST PARAMETER: THE LENGTH IS NOT NUMERIC

Type: User

 

04705 SEARCH: FIRST PARAMETER: THE DATA TYPE IS INCORRECT

Type: User

 

04707 SEARCH: FIRST PARAMETER: LENGTH AND DATA TYPE ARE INCOMPATIBLE

Type: User

 

04709 SEARCH: THE NUMBER OF PARAMETERS IS INCORRECT

Type: User

 

04710 CHECK: THE NUMBER OF PARAMETERS IS INCORRECT

Type: User

 

04711 SEARCH: THE FIRST AND SECOND PARAMETERS MUST BE CSTES

Type: User

 

04712 CHECK: THE FIRST PARAMETER MUST BE A CONSTANT

Type: User

 

04713 SEARCH: THE SECOND PARAMETER MUST CONSIST OF 2 CODED CHARACTERS

Type: User

 

04714 CHECK: THE FIRST PARAMETER MUST CONSIST OF 2 CODED CHARACTERS

Type: User

 

04715 SEARCH: THE VALUE OF THE SECOND PARAMETER IS INCORRECT

Type: User

 

04716 CHECK: THE VALUE OF THE FIRST PARAMETER IS INCORRECT

Type: User

 

04718 THE PHRASE CONTAINS TOO MANY SEARCH AND CHECK COMMANDS

Type: User

 

04721 $MONTH $DAY $YEAR: THE OPERAND MUST BE AN I.E. OR O.E. FIELD

Type: User

 

04722 $MONTH $DAY $YEAR: THE OPERAND MUST BE A DATE

Type: User

 

04723 $YEAR4: THE DATE MUST HAVE 8 CHARACTERS

Type: User

 

04725 %NBD -DAT %JULIAN: THE OPERAND MUST BE A DATE

Type: User

 

04726 %NBD -DAT %JULIAN: THE CONSTANT MUST BE A DATE

Type: User

 

04727 $MD, $D, $M, $, %, -: THE TABLE NAME IS UNKNOWN

Type: User

 

04728 $MD, $D, -, %NBD, -DAT: SYMBOL ";" IS MISSING

Type: User

 

04729 $MD, $M: THE POSITION IS NOT NUMERIC

Type: User

 

04730 $MD, $M: THE LENGTH IS NOT NUMERIC

Type: User

 

04731 $MD, $M: THE DATA TYPE IS INCORRECT

Type: User

 

04732 $MD, $M: THE LENGTH IS INCOMPATIBLE WITH THE DATA TYPE

Type: User

 

04735 $MD, $M: POSITION + LENGTH > TABLE VALUE SIZE

Type: User

 

04736 $MD, $M: THE FIRST PARAMETER IS INCORRECT

Type: User

 

04737 $MD, $M: THE NUMBER OF PARAMETERS IS INCORRECT

Type: User

 

04738 $MD, $M: THE FIRST PARAMETER MUST BE A CONSTANT

Type: User

 

04741 $MD, $M: THE KEY LENGTH IS INCORRECT FOR TABLE ACCESS

Type: User

 

04742 $MD, $M: THE KEY IS TOO LONG FOR TABLE ACCESS

Type: User

 

04743 $, $D, %, -: THE KEY LENGTH IS INCORRECT FOR TABLE ACCESS

Type: User

 

04744 $, $D, %, -: THE KEY IS TOO LONG FOR TABLE ACCESS

Type: User

 

04745 -VD : THE FIRST PARAMETER MUST BE "00" TO "19"

Type: User

 

04746 -VD : THE SECOND PARAMETER MUST BE "01" TO "20"

Type: User

 

04803 $SEARCH: THE FIRST PARAMETER IS INVALID

  • Type: User
  • Cause: The first parameter in the "SEARCH" function is invalid.
  • Action: The first parameter in the function is made up of the following:
    • Length of the return value (3 characters)
    • Data type of the return value (1 character)

 

04804 $SEARCH: FIRST PARAMETER: THE LENGTH IS NOT NUMERIC

  • Type: User
  • Cause: The first parameter in the "SEARCH" function is not valid ; a non-numeric value is linked with length.
  • Action: Modify the length linked to the "SEARCH" function.

 

04805 $SEARCH: FIRST PARAMETER: THE DATA TYPE IS INCORRECT

  • Type: User
  • Cause: The data type linked to the first parameter in the "SEARCH" function is not correct.
  • Action: Modify the return value data type.

 

04807 $SEARCH: FIRST PARAMETER: LENGTH AND DATA TYPE ARE INCOMPATIBLE

  • Type: User
  • Cause: The first parameter of the "SEARCH" function corresponds to the length of the return value ; if the data type is date, the length may be 6 or 7.

 

04809 $SEARCH: THE NUMBER OF PARAMETERS IS INCORRECT

  • Type: User
  • Cause: The number of parameters in the search function is incorrect.
  • Action: There are three parameters for the search function:
    • Length and data type of the return value
    • Module number
    • Search key

 

04810 $CHECK: THE NUMBER OF PARAMETERS IS INCORRECT

  • Type: User
  • Cause: The number of parameters in the check function is incorrect.
  • Action: There are two parameters for the check function:
    • Module number
    • Key (Input Event field, constant)

 

04811 $SEARCH: THE FIRST AND SECOND PARAMETERS MUST BE CSTES

  • Type: User
  • Cause: The first and second parameters in the search function must be constants.

 

04812 $CHECK: THE FIRST PARAMETER MUST BE A CONSTANT

  • Type: User
  • Cause: The first parameter in the check function must be a constant.

 

04813 $SEARCH: THE SECOND PARAMETER MUST CONSIST OF 2 CODED CHARACTERS

  • Type: User
  • Cause: In the search function, the second parameter must be between "01" and "99".

 

04814 $CHECK: THE FIRST PARAMETER MUST CONSIST OF 2 CODED CHARACTERS

  • Type: User
  • Cause: In the check function, the first parameter must be between "01" and "99".

 

04815 $SEARCH: THE VALUE OF THE SECOND PARAMETER IS INCORRECT

Type: User

 

04816 $CHECK: THE VALUE OF THE FIRST PARAMETER IS INCORRECT

Type: User

 

04818 THE PHRASE CONTAINS TOO MANY $SEARCH AND $CHECK COMMANDS

Type: User

 

04821 $MONTH $DAY $YEAR: THE OPERAND MUST BE AN I.E. OR O.E. FIELD

Type: User

 

04822 $MONTH $DAY $YEAR: THE OPERAND MUST BE A DATE

Type: User

 

04823 $YEAR4: THE DATE MUST HAVE 8 CHARACTERS

Type: User

 

04825 %NBD -DAT %JULIAN: THE OPERAND MUST BE A DATE

Type: User

 

04826 $NBD $CDAT $JULIAN: THE CONSTANT MUST BE A DATE

Type: User

 

04827 $ACCTAB, $EXTTAB, ETC.: THE TABLE NAME IS UNKNOWN

Type User

 

04828 $EXTTABD, $ACCTABD, $CHECKTABD, $NBJ, $CDAT: SYMBOL ";" MISSING

Type: User

 

04829 $EXTTABD, $EXTTAB: THE POSITION IS NOT NUMERIC

  • Type: User
  • Cause: The position for the "$EXTTABD" or "$EXTTAB" functions, is not expressed by a numeric value.
  • Action: For the following functions:
    • "$EXTTABD" : extract a field in internal table according to a given date
    • "$EXTTAB" : extract a field in internal table
  • The second parameter for these functions corresponds to the position, length and data type for the field; in this case it is necessary to correct the position because it is not expressed by a numeric value.

 

04830 $EXTTABD, $EXTTAB: THE LENGTH IS NOT NUMERIC

  • Type: User
  • Cause: The length for the "$EXTTABD" or "$EXTTAB" functions, is not expressed by a numeric value.
  • Action: For the following functions:
    • "$EXTTABD" : extract a field in internal table according to a given date.
    • "$EXTTAB" : extract a field in internal table.
  • The second parameter for these functions corresponds to the position, length and data type for the field; in this case it is necessary to correct the length because it is not expressed by a numeric value.

 

04831 $EXTTABD, $EXTTAB: THE DATA TYPE IS INCORRECT

  • Type: User
  • Cause: The data type for the "$EXTTABD or "$EXTTAB" functions, is not expressed correctly.
  • Action: For the following functions:
    • "$EXTTABD : extract a field in internal table according to a given date.
    • "$EXTTAB" : extract a field in internal table.
  • The second parameter for these functions corresponds to the position, length and data type for the field; in this case it is necessary to correct the data type because it is not expressed by one of the following values:
    • "A" : Alphanumeric
    • "N" : Numeric
    • "D" : Date

 

04832 $EXTTABD, $EXTTAB: THE LENGTH IS INCOMPATIBLE WITH THE DATA TYPE

  • Type: User
  • Cause: The data type for the "$EXTTABD" or "$EXTTAB" functions is alphanumeric and must not exceed 256 characters.

 

04835 $EXTTABD, $EXTTAB: POSIT + LENGTH > TABLE VALUE SIZE

  • Type: User
  • Cause: The position and length for the "$EXTTABD" or "$EXTTAB" functions do not correspond to the characteristics defined for this table.

 

04836 $EXTTABD, $EXTTAB: THE SECOND PARAMETER IS INCORRECT

  • Type: User
  • Cause: The second parameter for the "$EXTTABD" or "$EXTTAB" functions is incorrect.
  • Action: For the "$EXTTABD" or "$EXTTAB", the second parameter of these functions corresponds to the field position, length and data type.

 

04837 $EXTTABD, $EXTTAB: THE NUMBER OF PARAMETERS IS INCORRECT

  • Type: User
  • Cause: For the "$EXTTABD" or "$EXTTAB", the number of parameters is invalid

 

04838 $EXTTABD, $EXTTAB: THE SECOND PARAMETER MUST BE A CONSTANT

  • Type: User
  • Cause: For the "$EXTTABD" or "$EXTTAB" functions, the second parameter must always be a constant.

 

04841 $EXTTABD, $EXTTAB: THE KEY LENGTH IS INCORRECT FOR TABLE ACCESS

Type: User

 

04842 $EXTTABD, $EXTTAB: THE KEY IS TOO LONG FOR TABLE ACCESS

Type: User

 

04843 $ACCTAB, ETC: THE KEY LENGTH IS INCORRECT FOR TABLE ACCESS

Type: User

 

04844 $ACCTAB, ETC: THE KEY IS TOO LONG FOR TABLE ACCESS

Type: User

 

04845 $DATECNV : THE FIRST PARAMETER MUST BE "00" TO "19"

Type: User

 

04846 $DATECNV : THE SECOND PARAMETER MUST BE "01" TO "20"

Type: User

 

04999 THE ACCOUNTING INTEGRATOR DML IS RETAINED (CORRECT BUT NOTIFY THE HOT-LINE)

Type: User

Related Links