Is there a reason why access storage for IBM cloud or Amazon S3 is only directly supported with the INGEST, LOAD, BACKUP DATABASE, or RESTORE DATABASE commands, and no the log archiving LOGARCHMETH1 or LOGARCHMETH2 ?
Hi. At this stage it is a testing and demand statement. If interested please open a RFE/Idea so it can be assessed. Thanks.
IBM should manage ideas internally and not push their customer to do overwork, for features that might not even be implemented ... this was at least in the past the purpose of beta programs. LOGARCHMETH1=TSM is supported as well as BACKUP USE TSM. So why are you doing, again, partial implementation with S3. Production databases need backup and archive logs.
The more process you do, the less you deliver, this is no agile.
Best regards, JMB