Source System Availability Validation at Report Run Time

[FranklyOneZero]

Hi all.  I looked around this section of the forum and searched for some keywords but could not find another existing topic that fits my need. 

Can anyone share some possible approaches to this requirement?  We have several ETLs that are moving data using Informatica, scheduled by Autosys, from an on premise data warehouse, pushed to the IBM cloud to be consumed by Cognos.  We need to restrict access to reports that attempt to use data sources that have not yet refreshed as part of the nightly batch processing.  It seems like something that could be handled at the model level so I'm interested to find out if I should use a parameter map to drive the source system availability checks. 

We currently use an "ETL Status" table that will show the ETL name, ETLDateTime, and ETLBatchID and is maintained in the DB2 cloud environment.  What is the best way to restrict access to Cognos reports that attempt to consume data from tables involved in SourceSystemB (3/31 vintage), if the current date is 4/1? 

ETLName                   ETLDateTime   ETLBatchID
SourceSystemA   4/1/2017           2
SourceSystemB   3/31/2017   1
SourceSystemC   4/1/2017           2