By issuing db2 get db cfg for <database name> | find /i "first active log"" you'll learn the first log file since the last backup. Rollforward command may need any log file between that file and the currently active file.
db2 list history backup all for <database name> will tell you the range of log files created during an online backup. These will also be required for the database recovery.
You wrote: By issuing db2 get db cfg for <database name> | find /i "first active log"" you'll learn the first log file since the last backup.
As far as I have understood this parameter (loghead) indicates on the
lowest numbered log that is active and it dynamically is refreshed
during completion of transactions in a database.
You wrote: Rollforward command may need any log file between that file and the currently active file.
I am interested in what physical object (included in a structure,
databases) the information about the current unique identifier
of the completed transaction, on which DB2, should compare
with the same identifier at a level of tablespaces
(me a place the storage too interests it), to determine
whether is necessary rollforward of transactions on tablespaces to
recover a database in an consistent state?
From your answer and as I have understood independently,
this information is stored in the configuration file of a database. Whether so it?
Sorry, I don't know where this information is stored. Besides, you'll need to roll the database (or tablespaces) forward in any case, since everything will be in the ROLLFORWARD PENDING state after a restore.