Extract Utility User's Guide - Supra - Cincom
Extract Utility User's Guide - Supra - Cincom Extract Utility User's Guide - Supra - Cincom
Defining filesTo execute the Extract utility, you must define files for libraries, input, output,work, Directory, and PDM using the following file definitions. You do not needto read further unless you want more details about defining files.Extract Utility User's Guide, P25-9513-03 18Chapter: 3. Executing the Extract utilitySection: Defining files
File definitions in z/OSThese files are defined for you in the cataloged procedure TISUTUTL.Type of file Name of file Use of fileLibraries in z/OS STEPLIB In this data set concatenation, you declare thelibraries where the system looks for Extract's loadmodule and the single-task PDM load module.Input INPUT You code the UCL in this data set.XTRCTIN You code the XML for the Layout Control file in thisdata set. This describes the layout of the extractedoutput flat file. It also is the place to definesubfields.DTDLIB You refer to the Cincom-supplied DTD file with thisDD name.CSIPARM In this data set and in the SCHEMA and ENV-DESCstatements in the UCL control section, you code theinput to the single-task PDM.Output OUTPUT You define this data set to hold the status andprogress output listing that Extract creates.XTRCTOUT Extract writes the flat file output data in this file.SYSOUT You define this data set to hold output that theoperating system creates. XML processing errormessages can appear here.SYSTERM If you request extended execution tracing, thatoutput goes in this file.SYSUDUMP You define this data set to hold output from adump, if you request one.Work CSUWORK You define this data set for Extract to use as a workfile as it interprets and executes the UCL.Other files Directory You must define these files.PDMYou define one of these for each file that appearson a FILE statement in your UCL. If you are usingthe dynamic file allocation feature of PDM, you mayomit these file definitions.Extract Utility User's Guide, P25-9513-03 19Chapter: 3. Executing the Extract utilitySection: Defining files
- Page 2 and 3: SQL Access for SUPRA Server PDM ®E
- Page 5 and 6: 5. Coding the Extract function ....
- Page 7 and 8: OpenVMS installation and tailoringD
- Page 9 and 10: The FUNCTION statement initiates th
- 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: 3. Executing the Extract utilityOve
- 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
File definitions in z/OSThese files are defined for you in the cataloged procedure TISUTUTL.Type of file Name of file Use of fileLibraries in z/OS STEPLIB In this data set concatenation, you declare thelibraries where the system looks for <strong>Extract</strong>'s loadmodule and the single-task PDM load module.Input INPUT You code the UCL in this data set.XTRCTIN You code the XML for the Layout Control file in thisdata set. This describes the layout of the extractedoutput flat file. It also is the place to definesubfields.DTDLIB You refer to the <strong>Cincom</strong>-supplied DTD file with thisDD name.CSIPARM In this data set and in the SCHEMA and ENV-DESCstatements in the UCL control section, you code theinput to the single-task PDM.Output OUTPUT You define this data set to hold the status andprogress output listing that <strong>Extract</strong> creates.XTRCTOUT <strong>Extract</strong> writes the flat file output data in this file.SYSOUT You define this data set to hold output that theoperating system creates. XML processing errormessages can appear here.SYSTERM If you request extended execution tracing, thatoutput goes in this file.SYSUDUMP You define this data set to hold output from adump, if you request one.Work CSUWORK You define this data set for <strong>Extract</strong> to use as a workfile as it interprets and executes the UCL.Other files Directory You must define these files.PDMYou define one of these for each file that appearson a FILE statement in your UCL. If you are usingthe dynamic file allocation feature of PDM, you mayomit these file definitions.<strong>Extract</strong> <strong>Utility</strong> <strong>User's</strong> <strong>Guide</strong>, P25-9513-03 19Chapter: 3. Executing the <strong>Extract</strong> utilitySection: Defining files
Change language