HP 3000 Manuals HP 3000 Manuals
Identifying Non-Standard Features
The following table lists ALLBASE/SQL features that do not conform to the
FIPS 127.1 standard. These features do not generate a flagger warning.
Table 2-2. ALLBASE/SQL Non-Standard Programming Features
--------------------------------------------------------------------------------------------
| | |
| Feature | Description |
| | |
--------------------------------------------------------------------------------------------
| | |
| updatablility processing | Refer to the following section, "Understanding Implicit |
| | Updatability." |
| | |
--------------------------------------------------------------------------------------------
| | |
| SQLCA declaration | Refer to the following section, "Declaring the SQLCA." |
| | |
--------------------------------------------------------------------------------------------
| | |
| host language comments | ALLBASE/SQL allows host language comments within an SQL |
| | statement. The standard allows only SQL comments. |
| | |
--------------------------------------------------------------------------------------------
| | |
| $SQL COPY compiler | ALLBASE/SQL supports the COBOL COPY statement. Refer to the |
| directive | ALLBASE/SQL COBOL Application Programming Guide for usage |
| | details. |
| | |
--------------------------------------------------------------------------------------------
| | |
| SQLCODE in FORTRAN | The standard requires a variable declaration for SQLCOD, and |
| | ALLBASE/SQL supports the standard. |
| | |
--------------------------------------------------------------------------------------------
| | |
| SQLIND | This host variable type is not standards compliant. The |
| | standard requires that an indicator variable be declared as |
| | any exact numeric data type of scale zero, and ALLBASE/SQL |
| | supports the standard with the exception of BULK processing. |
| | |
--------------------------------------------------------------------------------------------