A couple things to consider:
1) Prognosis by default, unless you have changed the configuration, does not store the full PAN. We only show the first 6 and last 4 digits of the PAN. This is for general security and compliance with PCI. Changing this setting will bring your Prognosis infrastructure into the scope of PCI and is not recommended to be done adhoc and only be done under specific deployment conditions.
2) It sounds like you are trying to use the functions within TSV configuration. The TSV configuration allows you to essentially flag transactions based on very specific criteria and puts them in the "Transaction Exception" record when there is a hit and a label with what rule it was flagged for. You would NOT want to create a rule on an entire BIN range by itself. Though if you are looking at a specific BIN range under a specific set of circumstances so any rule is only hitting far less than 1% of your transactions then maybe that is something to consider using to generate a list. If you have a small list of very specific pans you can also put them in this configuration for flagging as a watchlist but TSV is not really designed to be a HOTCARD system will thousands or hundreds of thousands of pans. Out of the box displays then provide a list of any transaction flagged by the TSV rules. You have this functionality if you have TSV in your license.
3) Your payment switch or the system it offloads transactions is more suited to generating a list of ALL transactions that occurred on a BIN, though technically this and full transaction search is technically possible with Prognosis plus Prognosis Business Insight/Reporting.
If my answer helped you today, please be sure to mark the resolved button to assist others.
Christopher R Souser - Solution Architect – MSci. PA, CISSP, ITIL.