Spracherkennung für: .ted vermutete Sprache: Text {Text[116] SQL[223] Haskell[230]} [Methode: Schwerpunktbildung, einfache Gewichte, sechs Dimensionen]
! ----------------------------------------------------------------------
! IDENTIFICATION SECTION
! Standard COBOL Calling Module Language SQL
! ----------------------------------------------------------------------
!
sub *.* /59-byte ID/
/59-byte ID/___________________________________________________________/
!
! Document version of TEd used, for audit purposes.
!
sub *.* /TEd Version #/ -m
"TEd Version #"TEd Version $ver"
!
! ----------------------------------------------------------------------
! MAINTENANCE SECTION
! ----------------------------------------------------------------------
!
! Use the -t option on TEd to apply the official maintenance file.
! Then use a second -t option on TEd to apply this file.
! OR
! Insert the entire maintenance file in this position.
!
! ----------------------------------------------------------------------
! LOGIN SECTION
! ----------------------------------------------------------------------
!
! The login problem is solved here:
! If passwords are system-login passwords, then no changes are necessary.
! For other implementations, changes may be needed.
!
! For example, you may choose to code:
! rep *.sco /CALL "AUTHID"/
! CALL "AUTHID" USING SQLCODE uid
! ins< *.mco /PROCEDURE SUB1 SQLCODE/
! PROCEDURE AUTHID SQLCODE :UID CHAR(18);
! CONNECT :UID IDENTIFIED BY :UID;
!
! Other changes to establish the ANSI-standard environment would be coded here.
!
! ----------------------------------------------------------------------
! IMPLEMENTOR-DEFINED SECTION
! ----------------------------------------------------------------------
!
! Install implementor-defined precision of SQLCODE
! For example, to change precision from 9 to 4, code:
! sub *.sco /SQLCODE/
! /S9(9)/S9(4)/
!
! Install implementor-defined precision for indicator variable
! For example, to change precision from 4 to 2, code:
! sub *.sco /indic/
! /S9(4)/S9(2)/
! sub *.mco /INDIC/
! /(4)/(2)/
!
!
! Install vendor-supplied extensions to demonstrate FIPS Flagging:
! (Replace the underscores with vendor-supplied extensions.)
!
sub *flg005.*co //
/SUBSTR(EMPNAME,1,3) = 'Ali'/____________________/
/ABS(GRADE) = 12/________________/
!
! Change 18-character AUTHORIZATION ID to max supported in this DBMS/OS:
! sub *.* /CANWEPARSELENGTH18/
! /CANWEPARSELENGTH18/WECANPARSE12/
!
! Change COBOL programs to specify correct source and object computers
sub *.[ps]co /COMPUTER/
/xyz/_______________/
!
!
! ----------------------------------------------------------------------
! APPROVED CHANGES SECTION
! ----------------------------------------------------------------------
!
! Include here any changes approved by NIST for this validation:
!
! For example, to lengthen concurrency test #0230 (according to documentation),
! to allow interleaving for a DBMS using "burst" mode CPU allocation:
! sub *mp?001.[ps]* /keymax/ -i
! /50/300/
!
!
! ----------------------------------------------------------------------
! SYNTAX DEFICIENCIES SECTION
! ----------------------------------------------------------------------
!
!
! If a program cannot be executed because the precompiler issues
! a fatal syntax error message for a minor deficiency which is not
! the purpose of the test case, propose a change to NIST.
! A syntax change should be made to allow an SQL implementation
! to demonstrate functionality, i.e. semantic conformance.
! A global change will be counted as a single deficiency.
!
! ----------------------------------------------------------------------
! DELETED TESTS SECTION
! ----------------------------------------------------------------------
!
! If a program cannot be executed because the precompiler issues
! a fatal syntax error message for one of the tests, either propose a
! change to NIST or delete the entire test so that the rest of the tests
! in the program may execute. If this test is required, and not a FIPS
! Flagger test, it will appear as a deficiency on REPORT 4.
! Remember that if a cursor is defined in the test, then a separate
! delete command is needed for the cursor.
! For COBOL, a performed paragraph is found at the end of the program.
! So a separate delete command is needed for the performed paragraph.
!
! For example, to remove test number 278, code
! del *dml061.sco /BEGIN TEST0278/END TEST0278/
! del *dml061.mco /PROCEDURE SUB40/'0278','fail'/
! del *dml061.mco /PROCEDURE SUB45/COMMIT WORK/
!
!
[ Dauer der Verarbeitung: 0.136 Sekunden
]
