File Management - IBM

|
|
Table 3. High-Level Languages and Their OS/400 Operations (continued)
High-Level Languages
Operation
PASCAL PL/I
ILE RPG/400 Programming
Language
By key REWRITE KEY UPDATE
DELETE
By relative record number DELETE DELETE
By key DELETE KEY DELETE
ACQUIRE ACQ
RELEASE REL
COMMIT use CL COMMIT PLICOMMIT subroutine COMMIT
ROLLBACK use CL ROLLBACK PLIROLLBACK subroutine ROLBK
CLOSE CLOSE, END CLOSE, STOP CLOSE, RETURN
File security considerations
8 File Management V4R5
This section describes some of the file security functions. The topics covered
include the authorizations needed to use files and considerations for specifying
these authorities when creating a file. For more information about using the
security function on the system, see the Security - Reference or the Tips and Tools for
Securing Your AS/400, SC41-5300-04
Object authority
The following topics describe the types of authority that can be granted to a user
for a file. Also, you can use the SQL GRANT and REVOKE statements to assign
and remove these AS/400 authorities to SQL tables, including individual columns
within those tables. You can find information about these statements in the SQL
Reference book.
Object operational authority
Allows you to look at an object description and use the object as determined by
your data authorities to the object. Object operational authority is required to:
v Open the file for processing. You must also have read authority to the file. For
device files that are not using spooling, you must have object operational and
also all data authorities to the device.
v Compile a program which uses the file description.
v Display the file description.
v Delete the file.
v Transfer ownership of the file.