Author: Robert Sample
Posted: Fri May 20, 2016 1:56 am (GMT 5.5)
I found this CA-7 Support web site which says
so I suspect CA-7, at least, is intercepting the SMF15 record write and grabbing the data set name and so forth from there.
Dovetailed Technologies at http://community.dovetail.com/forum/viewtopic.php?t=901 talks about intercepting console messages with specific message ids.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Fri May 20, 2016 1:56 am (GMT 5.5)
I found this CA-7 Support web site which says
| Quote: |
| TROUBLESHOOTING: Reply to ICOM's WTOR with D=EXTDSN to make sure you see your newly added data set names. Perform the top-line command in CA 7. LCTLG,DSN=data.set.name (If CA 7 received the SMF type 15 record, the DATE and TIME the data set was created or updated appears here). Other References: TEC395371 - Procedure for updating CA 7 external data set tracking table. TEC395387 - Procedure for updating CA 7 external job tracking tables. Read more at http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec500384.aspx |
Dovetailed Technologies at http://community.dovetail.com/forum/viewtopic.php?t=901 talks about intercepting console messages with specific message ids.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth