If you run the following command you can get the log file path on the old server where the logs you need should be located. Note that if you are using archive logging, the archived logs may have been moved.
db2 get db config for database-name
Then you will see:
Path to log files = path
When you move the logs to the new server, you can also use the NEWLOGPATH directory command in the restore if necessary to specify where to find the log files if the path is different on the new server (see the Command Reference). I am not sure if you can reference a shared drive directly on the orginal server (so that you would not have to move any logs). This command only applies to the restore.
I think there may be a way to find out exactly which log files you need, but I don't know off-hand how to do that.
I am not sure what you are exactly asking about the database parms, but I would use the parms from the command above on the old server to set the parms on the new database as necessary if they don't get updated from the backup.
If you use an off-line backup and don't need to roll the logs forward past the backup image, you don't need any logs.