Page History
7.19.1 DATECHECK Parameters
|
|---|
Specifies the name of the field which is to be checked. Only fields of type Alpha, Packed, Signed, Date, or Datetime may be specified. Fields of any other type cannot be specified.
|
|---|
Specifies the format the date is expected in. The only permissible values are *SYSFMT, *DDMMYY, *MMDDYY, *YYMMDD, and *DDMMYYYY, *YYYYMMDD, *YYYYDDMM, *YYMM, *MMYY, *MMDDYYYY, *YYYYMM, *MMYYYY, *SYSFMT8.
...
If the specified field is of type Date or Datetime, this parameter is irrelevant as fields of type Date or Datetime are always in ISO format. So, if this parameter is specified as other than *SYSFMT, a FFC Warning is displayed stating that the format is ignored.
|
|---|
Specifies the number of days prior to the current date for which this date will still be valid. If no days are specified, the value 9999999 is assumed.
|
|---|
Specifies the number of days after the current date for which this date will still be valid. If no days are specified, the value 9999999 is assumed.
|
|---|
Specifies the action to be taken if the field is a valid date in the format nominated and also passes any associated range checking.If *NEXT is specified the field is considered to have passed the validation check. Processing will continue with the next RDML command.
...
If *ACCEPT is specified the field is considered to have passed the validation check AND no other validation checks will be performed against the field named in the FIELD parameter within this validation block. Processing continues with the next RDML command. However, if this is another validation check against the same field it will be effectively "disabled" and not performed.
|
|---|
Specifies the action to be taken if the date is not a valid date in the format nominated or fails any associated range checking.If *NEXT is specified the field is considered to have passed the validation check. Processing will continue with the next RDML command.
...
If *ACCEPT is specified the field is considered to have passed the validation check AND no other validation checks will be performed against the field named in the FIELD parameter within this validation block. Processing continues with the next RDML command. However, if this is another validation check against the same field it will be effectively "disabled" and not performed.
|
|---|
Allows up to 80 characters of message text to be specified. The message text specified should be enclosed in quotes. Use either the MSGTXT parameter or the MSGID / MSGF parameters but not both.
|
|---|
Allows a standard message identifier to be specified as the message that should be used. Message identifiers must be 7 characters long. Use this parameter in conjunction with the MSGF parameter.
|
|---|
Specifies the message file in which the message identified in the MSGID parameter will be found. This parameter is a qualified name. The message file name must be specified. If required the library in which the message file resides can also be specified. If no library name is specified, library *LIBL is assumed.
|
|---|
Use this parameter only in conjunction with the MSGID and MSGF parameters. It specifies from 1 to 20 values that are to be used to replace "&n" substitution variables in the message specified in the MSGID parameter.
...