beat heart disease without surgery a consumers guide to circulation therapy
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:beat heart disease without surgery a consumers guide to circulation therapy.pdf
Size: 4923 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 7 May 2019, 13:36 PM
Rating: 4.6/5 from 607 votes.
Status: AVAILABLE
Last checked: 5 Minutes ago!
In order to read or download beat heart disease without surgery a consumers guide to circulation therapy ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
beat heart disease without surgery a consumers guide to circulation therapyAll Rights Reserved This document contains unpublished, confidential, and proprietary information of Cincom. No disclosure or use of any portion of the contents of these materials may be made without the express written consent of Cincom. See for a list of Cincom trademarks and other trademarks that may appear in Cincom product documentation. All other trademarks are trademarks or registered trademarks of their respective companies. Cincom Systems, Inc. 55 Merchant Street Cincinnati, Ohio USA PHONE: (513) FAX: (513) WORLD WIDE WEB: Attention: Some Cincom products, programs, or services referred to in this publication may not be available in all countries in which Cincom does business. Additionally, some Cincom products, programs, or services may not be available for all operating systems or all product releases. Contact your Cincom representative to be certain the items are available to you. 3 Release information for this manual SQL Access for SUPRA Server PDM Extract Utility User's Guide, P, is dated September 1, This document supports Release 2.0 of SQL Access for SUPRA Server PDM. Cincom Technical Support for SQL Access for SUPRA Server PDM All customers Web: USA customers Phone: Fax: (513) Attn: SQL Access for SUPRA Server PDM Support Mail: Cincom Systems, Inc. This chapter contains the installation and tailoring instructions for this utility. MVS installation and tailoring During the CID Adapter Server installation, the files necessary for the Extract Utility were FTP d to the same PDS as the Adapter Server files. The EXTALLOC member should be run first to create the linklib and maclib for the Extract Utility. Add the Jobcard as you did when installing the CID Adapter Server. Then the EXTRECV member can be run to receive the linklib and maclib files that are in XMIT format. Extract Utility User's Guide, P Chapter: 1.http://daimarconstrucciones.com/images/admin/elica-igloo-ss-manual.xml
- Tags:
- beat heart disease without surgery a consumers guide to circulation therapy.
Installing the Extract utility Section: MVS installation and tailoring 7 OpenVMS installation and tailoring During the CID Adapter Server installation, the CSUNEXTR.ZIP file was FTP d to the same directory as the Adapter Server zip file. This zip file contains the executable for the Extract Utility. Use the unzip utility to unzip the file. The unzip utility is supplied on the freeware CD-ROM that comes with OpenVMS from HP. Extract utility overview The Extract utility allows you to identify standard SUPRA PDM database files from which you wish to extract data. They can be primary or related files, and you can take advantage of secondary keys. You also specify the layout of the records in the output flat file. Extract also performs data conversions you specify. Layout Control file. This file conforms to XML syntax rules. The UCL input tells Extract which files to extract data from, how to retrieve records from those files, and how to navigate from file to file to find data for extraction. The Layout Control file describes which fields to extract from the database files and their order in the records of the output flat file. It also allows you to subdefine a SUPRA database file s fields into subfields. You can also use the general utility cataloged procedure TISUTUTL. UCL is a procedural language that uses statements to identify the processing to be performed. The CONTROL statement initiates the control section, which establishes the processing environment for the Extract function. Extract Utility User's Guide, P Chapter: 2. Using the Extract utility Section: Extract utility overview 9 The FUNCTION statement initiates the Extract function. You can code the FUNCTION statement only once in a single UCL program. The following example shows how to organize a simple UCL program: CONTROL (BEGIN) supporting control statements FUNCTION (EXTRACT) supporting function statements CONTROL (END) Using the hierarchical structure of UCL UCL has a hierarchical structure.http://arnoldcosterexpeditions.com/userfiles/elica-ola-manual.xml After each CONTROL or FUNCTION statement, you code a number of subordinate statements. For example, in the following UCL program, LIST is subordinate to CONTROL, and FILE is subordinate to FUNCTION. This manual shows the subordinate statements by indenting them. CONTROL (BEGIN) LIST (name) FUNCTION (EXTRACT) FILE (name) CONTROL (END) To code a subordinate statement, you must code all of its superordinate statements. For example, you must code a FUNCTION statement before you code a FILE statement. This restriction also applies when subordinate statements have subordinates. In the following UCL example, the CONTROL statement has a subordinate statement, LIST, which has a subordinate statement, HEADER. You must code the LIST statement before you code the HEADER statement. CONTROL (BEGIN) LIST () HEADER(YES) FUNCTION (EXTRACT) STATISTICS (ALL) FILE (PTMF) QUALIFIER(SERIAL) SELECT(PTMFFELD.EQ.RANVCTRL) FILE (RANV) CONTROL (END) Extract Utility User's Guide, P Chapter: 2. Using the Extract utility Section: Extract utility overview 10 Formatting UCL UCL has a free-form format that allows almost any coding style. Even though this manual lists only one statement per line and indents to show subordination, you do not need to follow this structure. For example, you can code the following example this way: COMMAND (argument) STATEMENT (argument) STATEMENT (argument) STATEMENT (argument) Or this way: COMMAND (argument) STATEMENT (argument) STATEMENT (argument) STATEMENT (argument) When you put statements on the same line, you can put any number of spaces between them, or you can leave out spaces. You can also insert comments in your UCL program. You can provide any information you wish about your program in these comments. Whenever you code a subordinate statement to specify an option, however, you must also code the subordinate statement's superordinate statement even if you code it with a null argument. To code a null argument, put open and close parentheses after the statement. You do not need to include a space between them. The following is an example of a statement with a null argument: LIST () HEADER (YES) To code the HEADER statement, you must first code the LIST statement. If you were to code the HEADER statement without coding the LIST statement, you would receive an error message. Extract Utility User's Guide, P Chapter: 2. Using the Extract utility Section: Extract utility overview 12 Coding arguments When you code a statement name and an argument, you must enclose the argument in parentheses. You can use spaces or not as you like (but a single argument with multiple parts must not contain embedded spaces). For example, ELEMENT1 and ELEMENT 1 do not mean the same thing. Extract Utility User's Guide, P Chapter: 2. Using the Extract utility Section: Extract utility overview 13 Validating programs The program listing follows the opening message CSUL0101I: COMMENCING COMMAND VALIDATION. The listing is an image of your input program. These three indicators appear immediately after each line in which an error occurs. The pointer identifies the error's exact location in the line. The three-digit number specifies 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 is missing. The pointer is immediately below the file called CUST where the open parenthesis should be. Since only one error is reported in each line, nothing indicates that the close parenthesis is also missing. If a UCL programming error occurs, validation continues flagging errors to the end of the program. No function processing is done until you correct all errors and rerun the job. Extract Utility User's Guide, P Chapter: 2. Using the Extract utility Section: Extract utility overview 14 Executing utilities with different types of files You can execute the Extract utility with SUPRA PDM native files. Extract Utility User's Guide, P Chapter: 2. Using the Extract utility Section: Executing utilities with different types of files 15 Running debug and trace for DBA utilities Debug and trace facilities are available for the DBA Utilities. On occasion, you may need debug output to help your technical service center resolve a usage or production problem. Use Utility Control Language statements to activate debugging and tracing. 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 information DML returns a listing of Physical View DML CALL parameters FUNCTION returns the activities of all function processing TRACE returns logical calls Extract Utility User's Guide, P Chapter: 2. Using the Extract utility Section: Running debug and trace for DBA utilities 16 Using the XTRACE function The XTRACE function enables tracing in the utilities parser. Each modification of the parsing stack triggers a listing of the stack and other relevant information. This information provides a history of the parsing stack including pushing and popping of tokens according to the grammar rules. This information is meaningful only to Cincom engineering and support personnel, so you would be unlikely to use this option except with the help of Cincom personnel. Code the XTRACE parameter as follows: ON XTRACE ( ) OFF You may code XTRACE anywhere in a UCL program. You may enable the trace function for the entire UCL program or trace only a few statements in the program. Using extended execution tracing Extended execution tracing is a diagnostic tool that Cincom support personnel may 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. You must also define other files and code run-time options. This chapter discusses these topics. Extract Utility User's Guide, P Chapter: 3. Executing the Extract utility Section: Overview 18 Defining files To execute the Extract utility, you must define files for libraries, input, output, work, Directory, and PDM using the following file definitions. You do not need to read further unless you want more details about defining files. Input INPUT You code the UCL in this data set. XTRCTIN You code the XML for the Layout Control file in this data set. This describes the layout of the extracted output flat file. It also is the place to define subfields. DTDLIB You refer to the Cincom-supplied DTD file with this DD name. CSIPARM In this data set and in the SCHEMA and ENV-DESC statements in the UCL control section, you code the input to the single-task PDM. Output OUTPUT You define this data set to hold the status and progress 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 the operating system creates. XML processing error messages can appear here. SYSTERM If you request extended execution tracing, that output goes in this file. SYSUDUMP You define this data set to hold output from a dump, if you request one. Work CSUWORK You define this data set for Extract to use as a work file as it interprets and executes the UCL. Other files Directory You must define these files. PDM You define one of these for each file that appears on a FILE statement in your UCL. If you are using the dynamic file allocation feature of PDM, you may omit these file definitions. DTDLIB You may refer to the Cincom-supplied DTD file with this logical name (if defined), or include the full filespec (including path) in your XTRCTIN XML files. Output XTRCTOUT Extract writes the flat file output data in this file. Other files PDM You have one of these for each file that appears on a FILE statement in your UCL. On OpenVMS you must define logical names for XTRCTIN and XTRCTOUT. You must also indicate whether you want to print a dump or just messages. The last two interact with each other. To see the results of their possible combinations, see Results of different combinations of SPIE and DUMP on page 25. Follow the coding recommendations to avoid difficulty. TIP We recommend not coding this parameter. The Extract needs at least 400K. If you do not code this parameter, the default is the entire region. You will want to leave room in your region for loading other programs, such as the PDM or an exit program, so Cincom recommends that you always code this parameter. This parameter indicates whether the run-time interface should intercept program checks by the operating system. The default is SPIE, however, Cincom recommends coding NOSPIE (not intercept them). This parameter determines whether you get a dump when: The run-time interface intercepts a program check. If you coded NOSPIE, the run-time interface does not catch a program check and the operating system creates a dump. A run-time error occurs. If a run-time error occurs, you do not need a dump. The default is DUMP, however, Cincom recommends coding NODUMP. It stores some run-time information and all global variables. In addition, when each procedure starts, it allocates an area on the stack to store its local variables, and call and return information. As the procedure calls more nested procedures, the stack grows larger. As the nested procedures return, the stack grows smaller. Thus, the size of the stack depends on the levels of nesting in the procedure calls, and the number and size of the procedures' parameters and local variables. As the stack gets larger, it allocates space toward the heap area. The heap is the area that Extract dynamically allocates at run-time. Here, Extract stores internal context information, that is, variables that are not stored in the stack area. When Extract no longer needs the space, it is freed. As an area is freed, it can be reallocated. Thus, this area varies in size. When a procedure allocates the first heap area, it starts at the end of the space. When a procedure allocates a new area, it takes the new area from the space closer to the stack. It is best to use the STACK value of at least 400K. If this number proves to be insufficient, increase it as needed until Extract runs successfully. You know when the size is too small because you receive an error message and an abend code at run-time. The message states that the stack and heap have collided; that is, they are out of memory. To estimate how much larger to make the stack, consider the level of complexity in the UCL program. Complex tasks require more space. For example, if the files from which you extract data have extraordinarily large logical records, you may discover you need to increase the STACK value. Because the heap area is allocated dynamically, its size varies more than the stack and is harder to predict. The heap gets larger as the UCL gets more complex. The size of the heap depends on the number of control blocks Extract creates for internal use. You must begin by coding a control section. The control section defines the processing environment for Extract and can contain the following parts of the environment: The names of the database Schema and Environment Description The content and format of the output listing The sample UCL program below shows the names of the Schema and Environment Description. Within the control section, you can code exactly one FUNCTION statement to perform an extract. You begin the function statement with a FUNCTION command. (In this example, the function section has been abbreviated for clarity.) After the control and function sections, you code CONTROL (END). CONTROL (BEGIN) Initiates UCL program. ENV-DESC (MYDESC) Names Environment Description. SCHEMA (MYSCHEMA) Names Schema. FUNCTION (EXTRACT) Invokes the Extract function. CONTROL (END) Terminates program. Extract Utility User's Guide, P Chapter: 4. Coding the control section Section: Overview 29 Coding the UCL for the control section The following format and format descriptions show how to code a control section. You must always code CONTROL and FUNCTION statements. Most statements have supplied defaults; however, you must supply values for the SCHEMA and ENV-DESC statements. CONTROL ( BEGIN ) END ENV-DESC (environment-description-name) SCHEMA (schema-name) ABEND DIAGNOSTICS ( SIMPLE ) EXTENDED BEGIN END CONTROL ( ) Description Options Considerations Required. Marks the beginning and end of a utility control program. BEGIN END CONTROL (BEGIN) must be the first statement and CONTROL (END) must be the last statement in every program. If you code any statements before CONTROL (BEGIN), they cause an error in your program. If you code any after CONTROL (END), they are ignored. If you do not code an argument for CONTROL, you receive unpredictable results. Extract Utility User's Guide, P Chapter: 4. Coding the control section Section: Coding the UCL for the control section 30 ENV-DESC (environment-description-name) Description Format Considerations Required. Identifies the Environment Description and requests sign-on to the database. 1 8 alphanumeric characters. The first character must be alphabetic. This statement is required. The Schema and Environment Description combine to define the database to the Extract utility and the PDM. You must name your own Schema and Environment Description. You must also code a DIRECTORY parameter in the CSIPARM file. In the DIRECTORY parameter, name the bootstrap Schema and Environment Description used when the PDM initializes. Do not code the REALM parameter in the CSIPARM file. Identifies the Schema you want used for Extract. OPENVMS 6 character dbmod name. Considerations This statement is required. The Schema and Environment Description combine to describe the database to Extract and the PDM. ABEND EXTENDED DIAGNOSTICS ( SIMPLE ) Description Default Optional. Determines the type of diagnostic report to be provided on abnormal termination. EXTENDED Options ABEND You receive simple and extended diagnostics and a system dump when necessary. SIMPLE EXTENDED You receive simple diagnostics normally of only one line. You receive simple and extended diagnostics. Extract Utility User's Guide, P Chapter: 4. Coding the control section Section: Coding the UCL for the control section 32 5. Coding the Extract function Overview Use the Extract function when you want to extract records from one or more database files to a flat output file. FUNCTION (EXTRACT) FILE ( file-name ). ALL ELEMENT ( ) element-list Required. Invokes the Extract function. Required. Indicates the name of a file from which you want records extracted. 4 alphanumeric characters. Consideration You cannot code multiple file names (that is, FILE (file-name-list)) with one FILE statement. Instead you must code multiple FILE statements to request extraction of data from multiple files. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 35 DIRECT SERIAL QUALIFIER ( ) SEQUENTIAL INDEX Description Default Optional. Indicates the access mode you want Extract to use to access the current file. SERIAL Options DIRECT Reads a specific record either by RRN or by key. For more information, see considerations below. Considerations SERIAL Accesses the file serially without regard to chain sequence. SEQUENTIAL Accesses the related file sequentially by a specific linkpath. INDEX Accesses the file using a specific Secondary Key. Do not code QUALIFIER (SEQUENTIAL) for a primary file. As shown in the format, QUALIFIER has four options. Depending on the type of file (primary (P) or related (R)) and the access mode you code, the following statements are either required (r), optional (o), or invalid (i): QUALIFIER: DIRECT SERIAL SEQUENTIAL INDEX File Type: P R P R P R P R RRN i r i i i i i i LINKPATH i i i i i r i i KEY r i i i i o o o RRN-RANGE i i o o i i i i MAXIMUM i i o o i o o o SECONDARY-KEY i i i i i i r r If you code the QUALIFIER statement, you must put it before the RECORD statements. If you code a QUALIFIER(DIRECT) statement subordinate to the first FILE statement in your UCL, the function extracts only one record from the specified file. For subsequent FILE statements in your UCL, however, a subordinate QUALIFIER(DIRECT) statement extracts one record for each key value supplied from an earlier file. Therefore, multiple records may be extracted if multiple key values are passed by the program. If you code QUALIFIER (SEQUENTIAL) and the LINKPATH and KEY statements, the function extracts only the chain containing the key value you coded. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 36 If you code QUALIFIER (SEQUENTIAL) and the LINKPATH statement, but not the KEY statement, the function extracts all the chains associated with the linkpath. LINKPATH (access-linkpath) Restrictions Description Format Considerations You can use this statement only after a QUALIFIER (SEQUENTIAL) statement for a related file. In all other cases, it is invalid. Optional. Determines the access linkpath for a related file you are reading sequentially.If you code RECORD (ALL) with an access linkpath, that linkpath must exist in all records. You cannot code LINKPATH (linkpath-list). If you code the LINKPATH statement, you must put it before any RECORD statement. OPENVMS This is not a valid combination in OpenVMS if it is the first File in the UCL. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 37 D' dec-string' KEY ( X' hex-string' ) C' ' char-string Restrictions Description You can use this statement only after a QUALIFIER statement. Specifically, the following restrictions apply: After QUALIFIER(DIRECT). KEY is required for primary files but invalid for related files. The Extract function generates a KEY statement if you do not code one and you code a SELECT statement subordinate to the preceding FILE statement. After QUALIFIER(SERIAL). KEY is invalid. After QUALIFIER(SEQUENTIAL). KEY is invalid for primary files but optional for related files. After QUALIFIER(INDEX). KEY is optional. Indicates the key you want the function to use for direct access to a primary file, sequential access to a related file, or indexed access to either type of file. Format D'dec-string' A decimal string of 1 to 256 characters preceded by a D and surrounded by single quotes. This string is a byte key that must match the actual key length. X'hex-string' C'char-string' A hexadecimal string of 2 to 512 characters preceded by an X and surrounded by single quotes. This string is a byte key. The length must be an even number and twice the actual key length. A character string of 1 to 256 characters preceded by a C and surrounded by single quotes. This string is a byte key and must match the actual key length. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 38 Considerations If a character string contains one or more quotes, you must code two quotes for each actual quote. Any key you code must be the correct length for the file. If you code the KEY statement, you must put it before any RECORD statement. A KEY statement is automatically generated when the SELECT statement contains at least one control key field. This acts as a place holder for the key value passed from the previous FILE statement.This acts as a placeholder for the key value passed from the preceding FILE statement. RRN (record-rrn) Restrictions Description Format Considerations You can use this statement only after a QUALIFIER (DIRECT) statement for a related file. In all other cases, it is invalid. Optional. Selects a relative record number in a non-ksds related file that you want the function to read directly. 1 9 decimal characters You must code a record-rrn if you are extracting a related file and you coded QUALIFIER (DIRECT). You must code a record-rrn that is within the boundaries of the file. If you code the RRN statement, you must put it before any RECORD statement. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 39 low-rrn RRN - RANGE ( - high-rrn ) low-rrn - high-rrn Restrictions Description Format Do not use with key-sequenced data sets. You can use this statement only after a QUALIFIER (SERIAL) statement for a related file. In all other cases, it is invalid. Optional. Indicates a range of relative record numbers you want retrieved. The function does not retrieve records outside the range you code. 1 9 decimal characters for each rrn Options low-rrn Retrieves records having RRNs from low-rrn through the end of the file. Considerations -high-rrn low-rrn high-rrn Retrieves records having RRNs from the beginning of the file to high-rrn. Retrieves records having RRNs from low-rrn through high-rrn. If the low-rrn you code is not a valid data record, the function accesses the first data record with a higher RRN than the one you coded. If you are extracting a related file and the RRN you code is in the middle of a chain, the function does not extract prior records on that chain. If you code the RRN-RANGE statement, you must put it before any RECORD statement. MAXIMUM is optional if doing a select where a key value was passed; otherwise, it is invalid. MAXIMUM is optional. After QUALIFIER(SEQUENTIAL). MAXIMUM is invalid for primary files but optional for related files. This is equivalent to omitting the MAXIMUM statement. If you code the MAXIMUM statement, you must put it before any RECORD statement. The function includes in this count only valid data records that pass all other selection criteria. For example, if you specify an argument (via the CRITERIA statement), all data records must first pass the argument validation before the function adds them to the maximum record counter. If you code a value that exceeds the total number of records in this file, the function stops at the end of the file. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 41 SECONDARY-KEY(secondary-key) Restrictions Description Format Considerations You can use this statement only after a QUALIFIER statement. After QUALIFIER(INDEX), SECONDARY-KEY is required. After all other values of QUALIFIER, SECONDARY-KEY is invalid. Determines the secondary key to use during indexed access to a file.If you code the SECONDARY-KEY statement, you must put it before any RECORD statement. You can code any number of spaces before the element list, after END., and on either side of the separating commas. If you do not code END., the function considers the rest of the program as data. This is often an input coding error. Format for element One or more alphanumeric 8-character element names. You must make the first character in each name alphabetic and separate the names with commas. The rules for coding values of the KEY parameter (see above) apply to this value. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 42 Considerations for element If you code an element name in the argument, you must also code it in the ELEMENT statement unless you code ELEMENT (ALL). You cannot code a null element list in the CRITERIA argument. If you name an element in the CRITERIA argument, it must be in all the records you want extracted from the file. Options for operator Valid operators are as follows:.eq. Equal.NE. Not equal.gt. Greater than.lt. Less than.ge. Greater than or equal to.le. Less than or equal to Consideration for operator You must code a period before and after the Boolean operator. Only one operator may be specified. You must put a period before data value and END. after it. Considerations for datavalue You must make data values the same length as the element lengths in the element list. Do not put spaces or any other separator between data values. Your data may cross input line boundaries if necessary. The names f1elementn are names of Physical Fields occurring in the file identified by the FILE statement to which this SELECT statement is subordinate. The names f2elementn are names of Physical Fields occurring in the subsequent FILE statement. Considerations for element If you code an element name in the SELECT argument, you must also code it in the ELEMENT statement, unless you do not code the RECORD or ELEMENT statements but use the default for RECORD (ALL) and ELEMENT (ALL). If you name an element in the SELECT argument, it must be in all the records you want extracted from the file. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 44 Options for operator Valid operators are as follows:.eq. Equal.NE. Not equal.gt. Greater than.lt. Less than.ge. Greater than or equal to.le. Less than or equal to Consideration for operator You must code a period before and after the Boolean operator. Extract Utility User's Guide, P Section: Coding the UCL for the Extract function 45 RECORD ( ALL ) record-code Description Format Default Optional. Indicates the record codes of records from which you want data extracted. 2 alphanumeric characters ALL Options ALL Extracts from all records Considerations record-code Extracts from the specified record code only If you code this statement, you must code the ELEMENT statement.