Rule update errors

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

Rule update error messages

01502 01502 - Input form type <> PAR

  • Type User
  • Description Check the Input Form coding. The segment should start with PAR only

 

01503 Input form type <> RIN,RCR,RSC,REE,DEE,TAB,VRB

  • Type User
  • Description Check the Input Form coding . The segment must start with one of the following codes: RIN, RCR,RSC, REE, DEE, TAB

 

01504 All the invalid movements have not been displayed

  • Type Error
  • Description There are more than 100 Input Forms involved in the update procedure, not all of these have been printed.

 

01505 The file update is incorrect

  • Type User
  • Description Check the update code in relation to the Input Form code.

 

01506 The start date is not numeric

  • Type User
  • Description The date must be entered in the form of CYYMMDD

 

01507 The O.E. structure code is invalid

  • Type User
  • Description If the structure code is below 100, it must be justified to the right and supplemented by zeros to the left. Another possible cause: The content of the Input Form has shifted.

 

01508 The mapping rule number is not numeric

  • Type: User
  • Description: If the mapping rule number is below 10, it must be justified to the right and supplemented by zeros to the left. Another possible cause: The content of the Input Form has shifted.

 

01509 The mapping rule number is not 01 TO 50

  • Type: User

 

01510 The suffix must be blank or 01 to 20

Type: User

 

01513 The mapping rule already exists

Type: User

 

01515 Request to update a nonexistent mapping rule

Type: User

 

01516 The end date is not numeric

Type: User

 

01517 The workstation/host code is incorrect

Type: User

 

01518 The suffix must be blank or 01 to 90

Type: User

 

01519 The rule version does not exist

Type: User

 

01520 The rule version already exists

Type: User

 

01521 Unable to update the rule version (RGCLIN file)

Type: User

 

01522 Request to delete a nonexistent mapping rule

Type: User

 

01523 The start position for the I.E. is incorrect

Type: User

 

01524 The length of the I.E. descriptor is incorrect

Type: User

 

01525 The I.E. descriptor data type is incorrect

Type: User

 

01526 Request to delete nonexistent I.E. descriptors

Type: User

 

01528 Request to delete a nonexistent I.E. descriptor

Type: User

 

01529 Request to update a nonexistent I.E. descriptor

Type: User

 

01530 An I.E. descriptor already exists

Type: User

 

01532 The scenario number is not numeric

Type: User

 

01533 The scenario number is not 01 to 10

Type: User

 

01534 The scenario priority code is not numeric

Type: User

 

01536 The suffix must be C1 to C8 or E1 to E2

Type: User

 

01537 THE SCENARIO MAPPING RULE ORDER MUST BE BLANK OR 01 TO 50

Type: User

 

01538 REQUEST TO DELETE A NONEXISTENT SCENARIO

Type: User

 

01539 REQUEST TO UPDATE A NONEXISTENT SCENARIO

Type: User

 

01540 THE SCENARIO ALREADY EXISTS

Type: User

 

01542 THE FIELD NAME MUST NOT BE BLANK

Type: User

 

01543 THE START POSITION FOR THE O.E. DESCRIPTOR IS INCORRECT

Type: User

 

01544 THE LENGTH OF THE O.E. DESCRIPTOR IS INCORRECT

Type: User

 

01545 THE DATA TYPE FOR THE O.E. DESCRIPTOR IS INCORRECT

Type: User

 

01546 THE MANDATORY CODE IS INCORRECT

Type: User

 

01547 REQUEST TO DELETE A NONEXISTENT O.E. STRUCTURE

Type: User

 

01549 REQUEST TO DELETE A NONEXISTENT O.E. DESCRIPTOR

Type: User

 

01551 AN O.E. DESCRIPTOR ALREADY EXISTS

Type: User

 

01554 UNABLE TO WRITE AN O.E. DESCRIPTOR HEADER (DESCEE)

Type: Error

 

01555 THE SUFFIX MUST BE BLANK OR P1 TO P4

Type: User

 

01556 USER TABLE: THE KEY DATE IS NOT NUMERIC

Type: User

 

01557 USER TABLE: THE KEY LENGTH IS NOT NUMERIC

Type: User

 

01558 USER TABLE: THE VALUE LENGTH IS NOT NUMERIC

Type: User

 

01559 USER TABLE: ACCESS CODE = BLANK, Y,N

Type: User

 

01560 USER TABLE: VALUE DATA TYPE = A,N,D

Type: User

 

01561 USER TABLE: CANNOT BE MODIFIED, THE HEADER DOES NOT EXIST

Type: User

 

01562 USER TABLE: HEADER MODIFICATION WAS NOT AUTHORIZED

Type: User

 

01563 USER TABLE: REQUEST TO DELETE A NONEXISTENT TABLE

Type: User

 

01565 USER TABLE: REQUEST TO DELETE A NONEXISTENT ENTRY

Type: User

 

01566 USER TABLE: REQUEST TO MODIFY NONEXISTENT ENTRY

Type: User

 

01567 THE USER TABLE ALREADY EXISTS

Type: User

 

01569 PARAM.TABLE: UNABLE TO MODIFY, THE HEADER DOES NOT EXIST

Type: User

 

01570 PARAM.TABLE: UNAUTHORIZED HEADER MODIFICATION

Type: User

 

01571 PARAM.TABLE: REQUEST TO DELETE A NONEXISTENT TABLE

Type: User

 

01573 PARAM.TABLE: REQUEST TO DELETE A NONEXISTENT ENTRY

Type: User

 

01574 PARAM.TABLE: REQUEST TO MODIFY A NONEXISTENT ENTRY

Type: User

 

01575 THE PARAM.TABLE ALREADY EXISTS

Type: User

 

01577 THE RULE VERSION IS MISSING FOR THE I.E. DESCRIPTIONS

Type: User

 

01578 THE RULE VERSION IS MISSING FOR SOME SCENARIOS

Type: User

 

01579 THE RULE VERSION IS MISSING FOR SOME MAPPING RULES

Type: User

 

01580 THIS USER TABLE HAS NO HEADER

Type: User

 

01581 USER TABLE: THE ACCESS CODE IS INCORRECT

Type: User

 

01582 USER TABLE: KEY DATA TYPE = A,N,D

Type: User

 

01583 USER TABLE: IF VALUE DATA TYPE = D, LENGTH = 6,7,8

Type: Error

 

01584 USER TABLE: IF KEY DATA TYPE = D, LENGTH = 6,7,8

Type: Error

 

01585 USER TABLE: IF VALUE DATA TYPE = N, LENGTH <= 18

Type: Error

 

01586 USER TABLE: VALUE LENGTH <= 256

Type: Error

 

01587 USER TABLE: KEY LENGTH <= 17

Type: Error

 

01588 USER TABLE: THE ACCESS CODE FOR THIS ENTRY IS INCORRECT

Type: Error

 

01589 MOTRES PARAM.TABLE: MORE THAN 10 RESERVED WORDS

Type: Error

 

01590 THE INPUT MVT FILE SEGMENT HAS MORE THAN 15 ERRORS

Type: Error

 

01591 USER TABLE: THE KEY DOES NOT COMPLY WITH THE SPECIFICATIONS

Type: Error

 

01592 USER TABLE: THE VALUE DOES NOT COMPLY WITH THE SPECIFICATIONS

Type: Error

 

01593 THIS PARAM.TABLE HAS NO HEADER

Type: Error

 

01594 THE ACCESS CODE FOR THIS PARAM.TABLE IS INCORRECT

Type: Error

 

01595 PARAM.TABLE: KEY DATA TYPE = A,N,D

Type: User

 

01596 PARAM.TABLE: IF VALUE DATA TYPE = D, LENGTH = 6,7,8

Type: Error

 

01598 PARAM.TABLE: VALUE DATA TYPE = A,N,D

Type: User

 

01599 PARAM.TABLE: IF KEY DATA TYPE = D, LENGTH = 6,7,8

Type: Error

 

01600 PARAM.TABLE: IF VALUE DATA TYPE = N, LENGTH <= 18

Type: Error

 

01601 PARAM.TABLE: VALUE LENGTH <= 256

Type: Error

 

01602 PARAM.TABLE: KEY LENGTH <= 17

Type: Error

01603 PARAM.TABLE: THE ACCESS CODE FOR THIS ENTRY IS INCORRECT

Type: Error

 

01604 PARAM.TABLE: THE KEY DOES NOT COMPLY WITH THE SPECIFICATIONS

Type: Error

 

01605 PARAM.TABLE: THE VALUE DOES NOT COMPLY WITH THE SPECIFICATIONS

Type: Error

 

01606 THE DATE STRUCTURE IS INCORRECT

Type: User

 

01607 PARAM.TABLE: THE KEY LENGTH IS NOT NUMERIC

Type: User

 

01608 PARAM.TABLE: THE VALUE LENGTH IS NOT NUMERIC

Type: User

 

01609 USER TABLE: THE TABLE CHECK CODE IS INCORRECT

Type: User

 

01610 THE O.E. STRUCTURE CODE IS NOT ENTERED, THE HEADER MUST EXIST

Type: User

 

01611 THE O.E. STRUCTURE CODE MUST BE THE SAME AS THE HEADER'S

Type: User

 

01612 THE USER TABLE ENTRY VALUE ALREADY EXISTS

Type: User

 

01613 THE PARAM.TABLE ENTRY VALUE ALREADY EXISTS

Type: User

 

01614 NOT ALL MVTS WERE PRINTED: TOO MANY (>9999)

Type: Error

 

01615 THE RGCLCR FILE RULE IS MISSING

Type: Error

 

01616 THE RGCLEE FILE RULE IS MISSING

Type: Error

 

01617 THE RULE CODE MUST NOT BE BLANK

Type: Error

 

01618 THE SCENARIO MUST NOT BE DELETED WHEN THE UPDATE CODE IS ZERO

Type: Error

 

01619 THE TABLE NAME IS MISSING

Type: Error

 

01622 THERE IS NO SCENARIO FOR THIS RULE VERSION

Type: Error

 

01623 USER TABLE: A HEADER EXISTS, BUT HAS NO ENTRY

Type: Error

 

01625 NO KEY IS ALLOWED ON THE TABLE HEADER

Type: Error

 

01626 PARAM.TABLE: THE MOTRES TABLE IS MISSING

Type: Error

 

01628 THE POSITION OF THE I.E. ZONE IS OUT OF LIMITS

Type: User

 

01629 THE POSITION OF THE O.E. ZONE IS OUT OF LIMITS

Type: User

 

01642 THE VARIABLE NAME MUST NOT BE BLANK

Type: User

 

01643 THE VARIABLE NAME MUST NOT HAVE MORE THAN 10 CHARS

Type: User

 

01645 THE SUFFIX MUST BE P0 TO P4

Type: User

 

01646 THE LENGTH OF THE VARIABLE IS INCORRECT

Type: User

 

01647 THE VARIABLE DATA TYPE IS INCORRECT

Type: User

 

01648 THE RANGE CODE FOR THE VARIABLE IS INCORRECT

Type: User

 

01699 END OF INPUT FORM OVERFLOW

Type: Error

 

01700 THE PRINT POSITION FOR THE O.E. DESCRIPTOR IS NOT NUMERIC

Type: User

 

01701 THE PRINT POSITION FOR THE O.E. DESCRIPTOR IS INCORRECT

Type: User

 

01702 THE PRINT DETAIL CODE IS INCORRECT

Type: Error

 

01703 COPY: THE NEW RULE (OR VERSION) ALREADY EXISTS

Type: User

 

01708 COPY: CREATION ERROR IN RGCLSC

Type: User

 

01709 COPY: CREATION ERROR IN RGCLCR

Type: User

 

01710 COPY: CREATION ERROR IN RGCLEE

Type: User

 

01711 COPY: CREATION ERROR IN RGCLIN

Type: User

 

01712 REQUEST TO DELETE A NONEXISTENT RULE OR VERSION

Type: User

 

01713 COPY: RULE VERSION TO BE SPECIFIED

Type: User

 

01714 COPY: THE RULE OR VERSION TO BE COPIED DOES NOT EXIST

Type: User

 

01715 COPY: NEW VERSION DATE > VERSION DATE TO BE COPIED

Type: User

 

01724 NUMERIC CHECK CODE VALUES: Y,N,SPACE

Type: User

 

01725 BALANCING CHECK CODE VALUES: 0,1,2

Type: User

 

01726 THE SORT CRITERION ORDER NUMBER IS NOT NUMERIC

Type: User

 

01727 THE AGGREGATION CODE MUST BE: BLANK, 0 999, OR 60 TO 132

Type: User

 

01728 THE NUMBER OF DECIMAL PLACES MUST BE BLANK OR 0 TO 9

Type: User

 

01729 THE ZONE DATA TYPE IS NOT APPROPRIATE FOR AN AGGREGATION

Type: User

 

01730 AGGREG CODE + SORT CRITERIA DEFINED

Type: User

 

01731 TOO MANY SORT CRITERIA TO BE STORED - STRUCTURE CODE IGNORED :

Type: User

 

02003 THERE IS NO SEGMENT TO PROCESS

Type: User

 

02007 DATE MODULE PROBLEM

Type: Error

 

02011 THERE IS NO SCENARIO BY ACCOUNTS TO PRINT

Type: User

 

02014 THERE IS NO JOB REQUEST TO PROCESS

Type: User

 

02015 TOO MANY SIMULTANEOUS JOB REQUESTS

Type: User

 

02026 THE ERRINT AND I.E. FILES ARE INCONSISTENT

Type: Error

 

02027 THERE IS NO CORRECT I.E. FOR SOME GENERATED O.E.

Type: User

 

02028 THERE ARE NO GENERATED O.E. FOR SOME I.E.

Type: Error

 

02053 A FATAL ERROR OCCURRED WHEN MODULE ITR615 WAS CALLED

Type: Error

 

02055 THE HEADER LENGTH > I.E. LENGTH

Type: Error

 

02063 THIS STATUS IS NOT LISTED IN THE STATUS TABLE

Type: User

 

02066 THERE IS NO VALUE IN THE CDCRE TABLE --> I.E. IGNORED

Type: User

 

02999 THE FOLLOWING ERROR NUMBER IS NOT REFERENCED

Type: Error

Related Links