You can have KGUP store complementary key information when KGUP generates a key. This information includes the key value. You send the information to another system which uses the information to generate the complementary key. KGUP stores the key value to create the complementary key in either clear or encrypted form. KGUP stores information both in and not in the form of a control statement.
These statements show the syntax when you have KGUP store the complementary key value in clear form.
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(exporter,importer,ipinenc,opinenc, or pingen) CLEAR SINGLE
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(data) LENGTH(8) CLEAR
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(data) LENGTH(16) CLEAR
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(data) LENGTH(24) CLEAR
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(mac) OUTTYPE(mac or macver) CLEAR
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(datam) LENGTH(16) OUTTYPE(datam or datamv) CLEAR
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(pingen) LENGTH(8) CLEAR
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(exporter,importer,ipinenc,opinenc, or pingen) CLEAR
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(exporter or importer) CLEAR NOCV SINGLE
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(data) LENGTH(16) CLEAR NOCV
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(data) LENGTH(24) CLEAR NOCV
ADD or UPDATE LABEL(label) or RANGE(start-label,end-label),
TYPE(exporter or importer) CLEAR NOCV
ADD or UPDATE LABEL(label) TYPE(exporter or importer) CLEAR