Extract Utility User's Guide - Supra - Cincom

More documents

Recommendations

Info

Using the XTRACE functionThe XTRACE function enables tracing in the utilities’ parser. Each modificationof the parsing stack triggers a listing of the stack and other relevantinformation. This information provides a history of the parsing stack includingpushing and popping of tokens according to the grammar rules.This information is meaningful only to Cincom engineering and supportpersonnel, so you would be unlikely to use this option except with the help ofCincom personnel.Code the XTRACE parameter as follows:⎧ON⎫XTRACE ( ⎨ ⎬)⎩OFF⎭You may code XTRACE anywhere in a UCL program. You may enable the tracefunction for the entire UCL program or trace only a few statements in theprogram.Using extended execution tracingExtended execution tracing is a diagnostic tool that Cincom support personnelmay request that you run. It can be useful in debugging internal logic errors.You are unlikely to enable it except on advice from Cincom support personnel,who will ask that you send the output to them for analysis.Z/OSExtended execution tracing can be enabled by coding a value in the PARMparameter of the EXEC JCL statement, as follows:CSUNEXTR_T RACECALLS⎧YES⎫= ⎨ ⎬⎩ TRUE ⎭The output generated by this parameter also requires that you add thefollowing statement to your JCL://SYSTERM DD SYSOUT=*OPENVMSExtended tracing is enabled by defining a logical name:$ DEFINECSUNEXTR_TRACECALLS⎧YES⎫⎨ ⎬⎩TRUE⎭Extract Utility User's Guide, P25-9513-03 16Chapter: 2. Using the Extract utilitySection: Running debug and trace for DBA utilities
3. Executing the Extract utilityOverviewTo execute the Extract utility, you must supply UCL and the Layout Controlfile. You must also define other files and code run-time options. This chapterdiscusses these topics.Extract Utility User's Guide, P25-9513-03 17Chapter: 3. Executing the Extract utilitySection: Overview
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: Running debug and trace for DBA uti
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?