Must be coded as is. Indicates that PROCESS keywords follow.
Required keyword if SPECNAME is coded. Used as primary key for selection of a Selection Criteria Specification. This is the user ID or LTERM ID under which the specification was saved. USERID and UNLOAD are mutually exclusive.
Required keyword if UNLOAD is not coded. Used as secondary key for selection of a specification created using the online Selection Criteria Specification component. SPECNAME and UNLOAD are mutually exclusive.
Required keyword if SPECNAME is not coded. Used to unload (extract) the entire database accessible by the SRCSUB subschema. A specification is not used in this case. SPECNAME and UNLOAD are mutually exclusive parameters. In this case, SRCSUB is required and will be used at version 1 as both the source and target subschema.
Optional based upon whether you are using a transient subschema and whether the target dictionary requires a valid SIGNON statement. The user must have authority to add, delete, and punch load modules to/from the target dictionary.
Optional based upon whether the SIGNONID requires a sign-on password for the target dictionary.
Optional user-supplied name for the transient subschema used during CA IDMS Extractor load processing. If not specified, it defaults to:
Where:
The subschema name used by the Database Load Component is taken from this parameter regardless of whether or not a transient subschema is used. If a transient subschema is not used, specify the name of a subschema that the Database Load Component can successfully use.
Optional name of a subschema to be used by the Database Extract Component. Specifying a new source subschema allows the Database Extract Component to use a subschema that was not accessible to the online Selection Criteria Specification component but is almost identical to the original subschema. The subschema you specify must contain the same record and sets as the original subschema. The user records and sets must be in the same physical sequence in both subschemas (that is, they must be copied in the same order). If these conditions are not met, unpredictable results can occur.
Optional name of a DMCL to be used in conjunction with the SRCSUB subschema.
Optional name of the dictionary in which the SRCSUB subschema resides if the subschema is in a load area other than the primary dictionary specified for the CV that the Database Extract Component is going to use.
Optional name of a DMCL to use when the LOAD Component runs in LOCAL mode or when the DMCL named in TRANSSUB should not be used.
Optional name of a DDS node for the SRCSUB subschema. The name identifies the communication link between CVs and CPUs. Specifying this parameter indicates that CA IDMS accesses a CV that exists in a CPU other than the one it is to be executing under to retrieve the specified SRCSUB subschema.
Optional name of a DB name or segment for the SRCSUB subschema. The DB name or segment maps the logical subschema view to a physical database.
Optional name of a DDS node for the SRCSUB subschema. Specifying this parameter indicates that the Database Extract Component executes in a DDS environment and accesses a CV in another CPU.
Optional name of the user exit load module to be invoked whenever a database record meets its record level selection criteria.
Note: For more information, see Writing a User Exit Module--CUVUSRXA.
Optional parameter to indicate that the source and target subschemas are not to be compared. Use it if the target subschema is not accessible to the CV under which the Database Extract Component executes.
However, inconsistencies between the source and target subschemas can cause unpredictable results.
|
Copyright © 2013 CA.
All rights reserved.
|
|