OPTIONS DBMODE
The following values are valid for the OPTIONS
DBMODE
statement.
ADD
- The entire content of the object must be specified within Batch Loader statements and cannot exist already within the database (this is the default).
COPY
- An object and its segments can be identified for updating using
key fields (or
SAVELIST
), then only the fields that require changing need to be specified. If new values for key fields are given, a new object is created in the database and the original object is also kept in the database at completion. If an object with the same name already exists, theCOPY
fails. EXPORT
- An object is built from a combination of
TRANSLATE
and batch loader statements, then, instead of sending the object to the database, it is written out again as batch loader statements. In this way, input batch loader is translated to new batch loader, as part of life-cycle management, before applying to a database. REPLACE
- The entire content of the object must be specified within Batch Loader statements, but can already exist within the database and is replaced if an object with the same name and type already exists. If an object had been selected for replacing but given a new name for output, the original object is deleted from the database at completion.
UPDATE
- An object and its segments can be identified for updating using
key fields (or
SAVELIST
), then only the fields that require changing need to be specified. If the object does not already exist, theUPDATE
command acts likeADD
. If new values for key fields are given, a new object is created in the database and the original object is deleted from the database at completion.
Note:
- With
OPTIONS FIRST
andOPTIONS LAST
, you cannot useCOPY
andUPDATE
in conjunction withAUTOPRED
,AUTOSUCC
, orLINK
. - Under EQQYLTOP,
OPTIONS ACTION
is the equivalent toOPTIONS DBMODE
. Workload Automation Programming Language also recognizesOPTIONS ACTION
for backwards compatibility. UseOPTIONS DBMODE
to distinguish database between Record and Segment level actions.