Professional Documents
Culture Documents
Page 1
NK ELURU
Page 2
The Display File Description (DSPFD) command using TYPE(*MBR). This display
shows both date/times for the source member. The Last source update date/time value
should be used to compare to the Source file date/time value displayed from the
DSPOBJD command.
Note: If you are using the data written to output files to determine if the source and object dates
are the same, then you can compare the ODSRCD (source date) and ODSRCT(source
time) fields from the output file of the DSPOBJD DETAIL(*SERVICE) command to
the MBUPDD (member update date) and MBUPDT (member update time) fields from the
output file of the DSPFD TYPE(*MBR) command.
Page 3
NK ELURU
Page 4
For each file specified in the command, the database record contains:
o The name of the file, the name of the library containing the file, the file type, and
file member
o The file creation date and the number of record formats in the file
o The name of the record format used by the file, the format level identifier, the
format text description, the format record length, and the number of fields in the
format
o The information retrieval date and time
For each field in the record format, the record also contains the following, if applicable:
o The field name and external field name
o The type and length of the field
NK ELURU
Page 5
NK ELURU
Page 6
the name of the object's owner, the object's type, and a list of all the users who are
authorized to use the object
If an object does not have an owner name associated with it, no authorities for the object are
shown.
Restrictions:
1. The user must have object management authority to the object to use this command.
2. If the object is a file, the user must have object operational and object management
authorities.
NK ELURU
Page 7
Named users
Users (*PUBLIC) who do not have authority specifically given to them either for the
object or for the authorization list
If AUT(*AUTL) is specified, the PUBLIC authority for the object comes from the PUBLIC
authority of the authorization list securing the object. The AUTL parameter is used to secure an
object with an authorization list. User profiles cannot be secured by an authorization list
(*AUTL).This command can be used by an object's owner or by a user with object management
authority for the specified object. A user with object management authority can grant to other
users any authority that user has, except object management authority. Only the owner of the
object, or someone with all object special authority (*ALLOBJ), can grant object management
authority to a user. A user with *ALL authority can assign a new authorization list.
When granting authority to users, the REPLACE parameter indicates whether the authorities you
specify replace the user's existing authorities. The default value of REPLACE (*NO) gives the
authority that you specify, but it does not remove any authority that is greater than you specified,
unless you are granting *EXCLUDE authority. REPLACE(*YES) removes the user's current
authorities, then grants the authority that you specify.
When granting authority with a reference object, this command gives the authority that you
specify, but it does not remove any authority that is greater than you specified, unless you are
granting *EXCLUDE authority.
Restrictions:
1. This command must get an exclusive lock on a database file before read or object
operational authority can be given to a user.
NK ELURU
Page 8
NK ELURU
Page 9