Extract Utility User's Guide - Supra - Cincom

More documents

Recommendations

Info

IOBUF=yyyKCoding the run-time interface parametersAfter you set the amount of memory, code the following run-time parametersin any order. The last two interact with each other. To see the results of theirpossible combinations, see “Results of different combinations of SPIE andDUMP” on page 25. Follow the coding recommendations to avoid difficulty.Z/OS This parameter indicates the amount of storage to return to z/OS for I/Obuffers and control blocks after the STACK value is allocated. Since little of thefunction's I/O uses this storage, the 36K default is sufficient.TIP We recommend not coding this parameter.STACK=xxxKThis parameter sets the amount of storage for the run-time stack/heap. TheExtract needs at least 400K. If you do not code this parameter, the default isthe entire region.You will want to leave room in your region for loading other programs, such asthe PDM or an exit program, so Cincom recommends that you always code thisparameter.SPIE/NOSPIEFor further information and recommended values, see “Setting the z/OS STACKparameter” on page 26.This parameter indicates whether the run-time interface should interceptprogram checks by the operating system.The default is SPIE, however, Cincom recommends coding NOSPIE (notintercept them).DUMP/NODUMP You can use this parameter to indicate whether you want a dump of theaddress space in z/OS. This parameter determines whether you get a dumpwhen:♦♦The run-time interface intercepts a program check. If you coded NOSPIE,the run-time interface does not catch a program check and the operatingsystem creates a dump.A run-time error occurs. If a run-time error occurs, you do not need adump. The default is DUMP, however, Cincom recommends codingNODUMP.Extract Utility User's Guide, P25-9513-03 24Chapter: 3. Executing the Extract utilitySection: Choosing run-time options in z/OS
Run-timeoptionsResults of different combinations of SPIE and DUMPAction on abend generated byrun-time system (2506, astack/heap collision)Action on abend generated byoperating system (SOC1, anoperation exception)SPIE, DUMP Run-time system generates abend Run-time system catches abendRun-time system prints messages Run-time system may printmessagesRun-time system returns abendcode (2506)Run-time system prints dumpRun-time system returns abendcode (2531)Run-time system prints dumpSPIE, NODUMP Run-time system generates abend Run-time system catches abendRun-time system prints messages Run-time system may printmessagesRun-time system returns abendcode (2506)Run-time system prints no dumpRun-time system returns abendcode (2531)Run-time system prints no dumpNOSPIE, DUMP Run-time system generates abend Run-time system does not catchabendRun-time system prints messages Operating system performsabend logicNOSPIE, NODUMP(recommended)Run-time system returns abendcode (2506)Run-time system prints dumpRun-time system generates abendRun-time system prints messagesRun-time system returns abendcode (2506)Run-time system prints no dumpOperating system returns abendcode (50C1)Operating system may printdumpRun-time system does not catchabendOperating system performsabend logicOperating system returns abendcode (50C1)Operating system may printdumpExtract Utility User's Guide, P25-9513-03 25Chapter: 3. Executing the Extract utilitySection: Choosing run-time options in z/OS
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 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: Choosing run-time options in z/OSZ/
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?