The DBXSCNC procedure contains an instream data set that includes various parameters to control the load. The section of the procedure containing these parameters:
//PARMFILE DD *
STATUS1 ; 1. INSERT STATUS
STATUS2 ; 2. ALTERNATE SEARCH STATUS 1
STATUS3 ; 3. ALTERNATE SEARCH STATUS 2
DDL ; 4. USAGE
N ; 5. USE CREATOR
CREATOR ; 6. DEFAULT CREATOR
N ; 7. CHANGE DASH TO UNDERSORE = Y CHANGE UNDERSCORE
* TO DASH = U LEAVE ALONE = N
LANG ; 8. C = Assembler/VS 2 = Assembler II P = PLI A = ASSEMBLER
MEM ; 9. MEMBER NAME
N ; 10. DEBUG
B ; 11. IO VALIDATION
N ; 12. NO STRIP 88 LEVELS
S ; 13. SEARCH SYNONYM
B ; 14. USE ALIAS OR SYNONYM
* 15. THE NEXT PARM IS THE WORKSTION NAME WORKSTN;
Y ; 16. DYNAMIC CALL
1 ; 17. UNUSED
N ; 18. MULTIPLE PROGRAMS IN THIS JOB?
N ; 19. USE MEMBER
* Y OR N - STORE PROGRAM NAME AS INTERNAL NAME
* I - STORE MEMBER NAME AS INTERNAL NAME
N ; 20. NOT USED
N ; 21. USE LOCATION
LOCATION ; 22. DEFAULT LOCATION NAME FOR DB2 TABLES
DB2 ; 23. DBMS TYPE - VALID VALUES ARE:
* DB2, ORACLE, TERADATA. DB2 IS THE DEFAULT
Y ; 24. USE FIRST OBJECT.
* IN CASE OF SELECTING MULTIPLE ROWS FOR OBJECT:
* Y - USE FIRST ONE OBJECT AND PRODUSE WARNING MSG
* N - DON'T USE ANY OBJECT AND PRODUSE ERROR MESSAGE
/*
When you review the parameter file, remember the following considerations:
Descriptions of the parameters used in DBXSCNC follow.
|
Parameter |
Description |
|---|---|
|
Status 1 |
The load status of the parameter program. Before inserting entities based on the imported program, the scanner will check this status for existing object definitions whose attributes match those of the incoming object definitions. |
|
Status 2 or Status 3 |
(Optional) Alternate statuses for the loader to search (for existing instances) when it cannot find a reusable instance in Status 1. The loader checks Status 2 if it cannot find a match in Status1, and it checks Status 3 if it cannot find a match in Status 2. If the loader cannot find instances in any of the three statuses, it inserts a new instance into Status 1. Note: Using alternate statuses can result in performance degradation. |
|
Usage |
Tells the scanner which internal maps to use to process the incoming instances. For Assembler programs, always specify DDL. |
|
Use Creator |
Specifies whether to use the DB2 creators stored in the DB2 file when searching for COLUMN occurrences to link to PROGRAM. Because the Scan/Assembler process is heavily dependent upon the definitions inserted by the Catalog Synchronization facility, the value specified in this option should be consistent with the value specified in the Compare Creator option of the Catalog Synchronization facility, CatSync. If they differ, then Scan/Assembler may not be able to connect the PROGRAM occurrences to DB2 definitions. |
|
Default Creator |
This is the name you want to use as the creator when the creator in the DB2 file is blank. The loader will only use this information when you specify Y for User Creator (see previous table entry). |
|
Change Hyphens to Underscores |
Instructs the load program to use an _ (underscore) or a - (hyphen) as the delimiter. The options are: Y-if you want to translate a hyphen into an underscore N-if you want to leave the delimiter alone U-if you want to translate an underscore into a hyphen |
|
Load Language |
The programming language of the incoming metadata. Use A when loading scanned Assembler programs. Note: Load Language is used only when the program file (PRGFILE) does not contain a language. |
|
Member Name |
A name that will replace the name extracted from the program source. If you do not want to assign a new name, leave this field blank. |
|
Debug |
Allows you to produce DEBUG statements, which aids in troubleshooting. The debug output is sent to the data set you specify in the SYSPRINT file. |
|
I/O Validation |
The I/O Validation you want to use during processing. Options are: Y-Full Validation. Ensures that all entities inserted during the import process comply with your site status and code table standards. N-No Validation. Bypasses status checking and code table validation. Using No Validation dramatically increases the speed at which entities are processed. Entities inserted with invalid values must be corrected by the user before they are updated through standard edit procedures. You must have proper authorization to use this option. Only one batch job can be running with No Validation at any given moment. B-Batch Validation-the same as No Validation. CA recommends using Batch Validation. |
|
No Strip 88 Levels |
The field is not used for loading Assembler programs. |
|
Search Synonym |
N-To search for tables and views only A-To search for aliases and synonyms only S-To search for tables, views, synonyms, then aliases |
|
Use Alias or Synonym |
S-To use synonyms A-To use aliases B-To use both Note: Use Alias or Synonym only when search synonyms are set to A or S. |
|
Workstation Name |
Allows you to specify a workstation name into which all of the components of the Assembler program are placed during the load. |
|
Dynamic Call |
Allows you to specify whether to process programs in the linkage file where the program name is a variable name. N-if you do not want to load variable names as programs from the linkage file. Y-if you want to load variable names as programs from the linkage file. |
|
Unused |
Not used for Loading Assembler programs. |
|
Multiple Programs in this Job |
Y-if you are scanning more than one program. N-if you are not scanning more than one program. |
|
Use Member |
Y-The program name is derived from the member name if specified; otherwise, the program name is derived from the first eight characters of the PRGFILE input data set The internal name in the Program object is derived from the first eight characters of the PRGFILE input data set I-The program name in the Program object is derived from:
The internal name in the program object is derived from:
|
|
Use Location |
Y-To use the DB2 Location name stored in the DB2 file when searching for COLUMN occurrences to link to PROGRAM. N-To ignore the DB2 Location name. Because the CA Repository Exchange for Assembler process is heavily dependent upon the definitions inserted by the Catalog Synchronization Facility, the value specified in this option should be consistent with the value specified in the Qualification level option of the CatSync. If the values differ, then CA Repository Exchange for Assembler may not be able to connect the PROGRAM occurrences to DB2 definitions. Note: If you use a qualification level of F when running the Catalog Synchronization Facility, Use Location should be set to Y. |
|
Location |
The name to use as the location when the location in the SQL file is blank The loader only uses this information when you specify Y for the Use Location parameter (see previous parameter). |
|
RDBMS Type |
One of the following: DB2-To search for column information based on the DB2_COLUMN_NAME in the Element Object ORACLE-To search for column information based on the ORACLE_COLUMN_NAME in the Element Object TERADATA-To search for column information based on the TERDAT_COLUMN_NAME in the Element Object |
|
Use First Object |
Y-To have the Load program relate the program to the first of any duplicate elements that meets the selection criteria for resolving duplicates when more then one result row is returned. N-To produce a warning message indicating that the result was not found because of duplicates |
Note: If the PROGRAM occurrence is not found in the primary status, the load program always inserts the PROGRAM definition into the primary status. It never inserts the definition into one of the alternate statuses.
| Copyright © 2009 CA. All rights reserved. | Email CA about this topic |