Extract Utility User's Guide - Supra - Cincom

More documents

Recommendations

Info

2. Using the Extract utilityYou can use the Extract utility to retrieve data from a SUPRA PDM database andreformat it into a flat file suitable for input to a data warehouse application,such as CincomBI for SUPRA.Extract utility overviewThe Extract utility allows you to identify standard SUPRA PDM database filesfrom which you wish to extract data. On z/OS these can be SUPRA native,converted, or Series 80 files. They can be primary or related files, and you cantake advantage of secondary keys. You also specify the layout of the records inthe output flat file. Extract also performs data conversions you specify.You supply three input control files:Z/OS ♦ CSIPARM file (z/OS only). Described in the SUPRA Server PDM and DirectoryAdministration Guide (OS/390 & VSE), P26-2250.♦ Utility Control Language (UCL). Described in more detail in Chapters "4.Coding the control section" on page 28 and "5. Coding the Extract function"on page 32.♦Layout Control file. Described in more detail in Chapter "5. Coding theExtract function" on page 32. This file conforms to XML syntax rules.The UCL input tells Extract which files to extract data from, how to retrieverecords from those files, and how to navigate from file to file to find data forextraction. The Layout Control file describes which fields to extract from thedatabase files and their order in the records of the output flat file. It alsoallows you to subdefine a SUPRA database file’s fields into subfields.Z/OSYou submit the UCL program and Layout Control file by executing theCSUNEXTR load module in z/OS. You can also use the general utility catalogedprocedure TISUTUTL. For more information, refer to the SUPRA Server PDM andDirectory Administration Guide (OS/390 & VSE), P26-2250.You define two output files:♦♦Status and progress listing fileExtracted output flat fileOverview of UCLTo program the Extract utility function, you must use UCL. UCL is a procedurallanguage that uses statements to identify the processing to be performed. TheCONTROL statement initiates the control section, which establishes theprocessing environment for the Extract function.Extract Utility User's Guide, P25-9513-03 8Chapter: 2. Using the Extract utilitySection: Extract utility overview
The FUNCTION statement initiates the Extract function. You can code theFUNCTION statement only once in a single UCL program. The following exampleshows how to organize a simple UCL program:CONTROL (BEGIN)supporting control statementsFUNCTION (EXTRACT)supporting function statementsCONTROL (END)Using the hierarchical structure of UCLUCL has a hierarchical structure. After each CONTROL or FUNCTION statement,you code a number of subordinate statements. For example, in the followingUCL program, LIST is subordinate to CONTROL, and FILE is subordinate toFUNCTION. This manual shows the subordinate statements by indenting them.CONTROL (BEGIN)LIST (name)FUNCTION (EXTRACT)FILE (name)CONTROL (END)To code a subordinate statement, you must code all of its superordinatestatements. For example, you must code a FUNCTION statement before youcode a FILE statement. This restriction also applies when subordinatestatements have subordinates. In the following UCL example, the CONTROLstatement has a subordinate statement, LIST, which has a subordinatestatement, HEADER. You must code the LIST statement before you code theHEADER statement.CONTROL (BEGIN)LIST ()HEADER(YES)FUNCTION (EXTRACT)STATISTICS (ALL)FILE (PTMF)QUALIFIER(SERIAL)SELECT(PTMFFELD.EQ.RANVCTRL)FILE (RANV)CONTROL (END)Extract Utility User's Guide, P25-9513-03 9Chapter: 2. Using the Extract utilitySection: Extract utility overview
Page 2 and 3: SQL Access for SUPRA Server PDM ®E
Page 5 and 6: 5. Coding the Extract function ....
Page 7: OpenVMS installation and tailoringD
Page 11 and 12: Coding null argumentsDefault values
Page 13 and 14: Validating programsThe program list
Page 15 and 16: Running debug and trace for DBA uti
Page 17 and 18: 3. Executing the Extract utilityOve
Page 19 and 20: File definitions in z/OSThese files
Page 21 and 22: File definitions in OpenVMSYou must
Page 23 and 24: Choosing run-time options in z/OSZ/
Page 25 and 26: Run-timeoptionsResults of different
Page 27 and 28: Estimating the size of the stack/he
Page 29 and 30: Coding the UCL for the control sect
Page 31 and 32: SCHEMA (schema-name)Description Req
Page 33 and 34: Coding the UCL for the Extract func
Page 35 and 36: ⎡DIRECT⎤⎢SERIAL⎥QUALIFIER (
Page 37 and 38: ⎧D'dec-string'⎫⎪⎪KEY ( ⎨X
Page 39 and 40: ⎡low-rrn⎤⎢⎥RRN - RANGE (⎢
Page 41 and 42: SECONDARY-KEY(secondary-key)Restric
Page 43 and 44: SELECT (f1element1[,f1element2,...,
Page 45 and 46: ⎧RECORD ( ALL ⎫⎨⎬)⎩record
Page 47 and 48: ♦Additional constraints apply in
Page 49 and 50: This section explains the detailed
Page 51 and 52: RestrictionsDescriptionFormatConsid
Page 53 and 54: Format=”field-format-mask” Opti
Page 55 and 56: Considerations♦♦♦♦♦Each X
Page 57 and 58: Displacement=”subfield-displaceme
Page 59 and 60:
Extract examplesThe examples in thi
Page 61 and 62:
The output report listing is:---TTT
Page 63 and 64:
The output report listing is:1TIS/X
Page 65 and 66:
The first few records of the extrac
Page 67 and 68:
The output report listing is:---TTT
Page 69 and 70:
The first few records of the extrac
Page 71 and 72:
Extract Utility User's Guide, P25-9
Page 73 and 74:
0 CSUL0307I : ALL CONTROL SECTIONS
Page 75 and 76:
IndexAaccess linkpathspecifying for
Page 77:
STEPLIB filez/OS 19storage 23supero
show all

Extract Utility User's Guide - Supra - Cincom

Create successful ePaper yourself

Delete template?

Save as template?