Extract Utility User's Guide - Supra - Cincom
Extract Utility User's Guide - Supra - Cincom Extract Utility User's Guide - Supra - Cincom
Coding argumentsWhen you code a statement name and an argument, you must enclose theargument in parentheses. You can use spaces or not as you like (but a singleargument with multiple parts must not contain embedded spaces). Forexample, all of the following statement formats are valid:STATEMENT(argument)STATEMENT (argument)STATEMENT ( argument )STATEMENT ()STATEMENT ( )STATEMENT()If the format shows the argument can be a list, it looks like the followingexample:⎛⎧ALL⎫⎞ELEMENT ⎜⎟⎨⎬⎝⎩element-list⎭⎠If you code a list of elements instead of ALL, separate the elements withcommas, as shown in the following example:ELEMENT(ELEMENT1,ELEMENT2,ELEMENT3)You can also separate the items in a list with any number of spaces, as shownin the following examples:ELEMENT (ELEMENT1, ELEMENT2, ELEMENT3)ELEMENT (ELEMENT1, ELEMENT2, ELEMENT3)Do not embed spaces within an item. For example, ELEMENT1 and ELEMENT 1do not mean the same thing.Extract Utility User's Guide, P25-9513-03 12Chapter: 2. Using the Extract utilitySection: Extract utility overview
Validating programsThe program listing follows the opening message CSUL0101I: COMMENCINGCOMMAND VALIDATION. The listing is an image of your input program.Errors are identified by an error flag (**ERROR**), error pointer (@), and athree-digit number. These three indicators appear immediately after each linein which an error occurs. The following annotated listing identifies errors inlines 18 and 21:Line number Line text Indicator1 CONTROL (BEGIN) Valid Command2 ENV-DESC (MYDESC) Valid Command..17 FUNCTION (EXTRACT) Valid Command18 FILE CUST Invalid Command**ERROR** @001 Inserted Error InformationError NumberError Pointer19 RECORD (ALL) Valid Command20 ELEMENT (ALL) Valid Command21 FILE (ABC#) Invalid Command**ERROR** @015 Inserted Error InformationError NumberError Pointer..44 CONTROL (END) Valid CommandThe error flag appears in the line number column in the left margin. Thepointer identifies the error's exact location in the line. The three-digit numberspecifies the error's cause or condition. Only one error is reported in each line.For example, in line 18, the number 001 indicates the open parenthesis ismissing. The pointer is immediately below the file called CUST where the openparenthesis should be. Since only one error is reported in each line, nothingindicates that the close parenthesis is also missing.If a UCL programming error occurs, validation continues flagging errors to theend of the program. No function processing is done until you correct all errorsand rerun the job.Extract Utility User's Guide, P25-9513-03 13Chapter: 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 and 8: OpenVMS installation and tailoringD
- Page 9 and 10: The FUNCTION statement initiates th
- Page 11: Coding null argumentsDefault values
- 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
Coding argumentsWhen you code a statement name and an argument, you must enclose theargument in parentheses. You can use spaces or not as you like (but a singleargument with multiple parts must not contain embedded spaces). Forexample, all of the following statement formats are valid:STATEMENT(argument)STATEMENT (argument)STATEMENT ( argument )STATEMENT ()STATEMENT ( )STATEMENT()If the format shows the argument can be a list, it looks like the followingexample:⎛⎧ALL⎫⎞ELEMENT ⎜⎟⎨⎬⎝⎩element-list⎭⎠If you code a list of elements instead of ALL, separate the elements withcommas, as shown in the following example:ELEMENT(ELEMENT1,ELEMENT2,ELEMENT3)You can also separate the items in a list with any number of spaces, as shownin the following examples:ELEMENT (ELEMENT1, ELEMENT2, ELEMENT3)ELEMENT (ELEMENT1, ELEMENT2, ELEMENT3)Do not embed spaces within an item. For example, ELEMENT1 and ELEMENT 1do not mean the same thing.<strong>Extract</strong> <strong>Utility</strong> <strong>User's</strong> <strong>Guide</strong>, P25-9513-03 12Chapter: 2. Using the <strong>Extract</strong> utilitySection: <strong>Extract</strong> utility overview
Change language