Page History
7.35.1 DELETE Parameters
|
|---|
Refer to Specifying File Names in I/O Commands.
|
|---|
Refer to Specifying Conditions and Expressions and Specifying WHERE Parameter in I/O Commands.
|
|---|
Refer to Specifying File Key Lists in I/O Commands.
For details of how using this parameter can affect automatic "cross update" checking, refer to the Delete Comments/Warnings section.
|
|---|
Specifies the name of a field that is to receive the "return code" that results from the I/O operation.
...
For values, refer to I/O Return Codes.
|
|---|
Specifies what action is to be taken if an I/O error occurs when the command is executed.
...
*NEXT indicates that control should be passed to the next command. The purpose of *NEXT is to permit you to handle error messages in the RDML, and then ABORT, rather than use the default ABORT. (It is possible for processing to continue for LANSA for i and Visual LANSA, but this is NOT a recommended way to use LANSA.)
ER returned from a database operation is a fatal error and LANSA does not expect processing to continue. The IO Module is reset and further IO will be as if no previous IO on that file had occurred. Thus you must not make any presumptions as to the state of the file. For example, the last record read will not be set. A special case of an IO_ERROR is when a trigger function is coded to return ER in TRIG_RETC. The above description applies to this case as well.
Therefore, LANSA recommends that you do NOT use a return code of ER from a trigger function to cause anything but an ABORT or EXIT to occur before any further IO is performed.
...
If none of the previous values are used you must nominate a valid command label to which control should be passed.
|
|---|
Specifies the action to be taken if a validation error was detected by the command.
...
The *LASTDIS is valid even if there is no "last display" (such as in batch functions). In this case the function will abort with the appropriate error message(s).
When using *LASTDIS the "Last Display" must be at the same level as the database command (INSERT, UPDATE, DELETE, FETCH and SELECT). If they are at different levels e.g. the database command is specified in a SUBROUTINE, but the "Last Display" is a caller routine or the mainline, the function will abort with the appropriate error message(s).
The same does NOT apply to the use of event routines and method routines in Visual LANSA. In these cases, control will be returned to the calling routine. The fields will display in error with messages returned to the first status bar encountered in the parent chain of forms, or if none exist, the first form with a status bar encountered in the execution stack (for example, a reusable part that inherits from PRIM_OBJT).
|
|---|
Specifies what is to happen if no record is found in the file that has a key matching the key nominated in the WITH_KEY parameter.
...
If none of the previous values are used you must nominate a valid command label to which control should be passed.
|
|---|
Specifies whether a "not found" message is to be automatically issued or not.
...
The only other allowable value is *YES which indicates that a message should be automatically issued. The message will appear on line 22/24 of the next screen format presented to the user or on the job log of a batch job.
|
|---|
Specifies the name of a field that contains the relative record number (for relative record file processing) of the record which is to be deleted. The WITH_RRN parameter cannot be used if the WITH_KEY or WHERE parameters are used.
...
7.35.2 DELETE Comments / Warnings for details of how using this parameter can affect automatic "cross update" checking.
Load Other File in the Visual LANSA Developers Guide.
|
|---|
Specifies the name of a field in which the relative record number of the record just deleted should be returned. The value returned in this field is not usable when the DELETE command is deleting multiple records from the file.
...
For further information refer also to Load Other File in the Visual LANSA Developers Guide.
|
|---|
Indicates whether the I/O operation should actually be performed or only "simulated" to check whether all file and data dictionary level validation checks can be satisfied when it is actually performed.
...
*YES indicates that the I/O operation should be simulated to verify that all file and data dictionary level checks can be satisfied. The database file involved is not changed in any way when this option is used.
|
|---|
This parameter was made redundant in LANSA release 4.0 at program change level E5.
...
Portability Considerations | If using Visual LANSA, refer to Commitment Control in the LANSA Application Design Guide. |
|
|---|
Specifies the name of a field that contains the update id column to be compared with the update id column of the row to be deleted.
...