Extract Utility User's Guide - Supra - Cincom

More documents

Recommendations

Info

Executing utilities with different types of filesYou can execute the Extract utility with SUPRA PDM native files. On z/OShowever, you can also execute it with Series 80 or SUPRA converted files.Extract Utility User's Guide, P25-9513-03 14Chapter: 2. Using the Extract utilitySection: Executing utilities with different types of files
Running debug and trace for DBA utilitiesDebug and trace facilities are available for the DBA Utilities. On occasion, youmay need debug output to help your technical service center resolve a usage orproduction problem. Use Utility Control Language statements to activatedebugging and tracing.Z/OSIn z/OS environments, the debug or trace output goes to the same output fileas the standard progress and status listing output. This file is specified by the//OUTPUT DD statement://OUTPUT DD SYSOUT=*Using the DEBUG functionThe DEBUG function causes the Extract utility to print debugging informationduring utility execution. DEBUG produces a substantial amount of output.The DEBUG parameter must be part of the CONTROL section of a UCL program.Code the parameter as follows:⎧ALL⎫⎪DML⎪DEBUG ( ⎨ ⎬)⎪FUNCTION⎪⎪⎩TRACE⎪⎭where:♦♦♦♦ALL returns all types of debugging informationDML returns a listing of Physical View DML CALL parametersFUNCTION returns the activities of all function processingTRACE returns logical callsExtract Utility User's Guide, P25-9513-03 15Chapter: 2. Using the Extract utilitySection: Running debug and trace for DBA utilities
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: Validating programsThe program list
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?