Re: Tracking called (non-main) programs using SMF records

2019-11-15 Thread Bernd Oppolzer
This does not give you call relations, where programs are statically linked. And static analysis (related on source code) does not give you relations, where the name of the callee comes from a table or is computed at run time. That's what a former customer did (besides static analysis, which wa

Re: Tracking called (non-main) programs using SMF records

2019-11-14 Thread Beverly Caldwell
Write your own CSV exit to knock out an SMF record for these called programs. I have done this several times and only once missed anything because some smartie pants from CA was doing his own program loads. On Thu, Nov 14, 2019 at 3:59 AM Massimo Biancucci wrote: > Hi, > > as other colleagues al

Re: Tracking called (non-main) programs using SMF records

2019-11-14 Thread Massimo Biancucci
Hi, as other colleagues already said, no standard SMF way. At my customers sites, they use TADz (it seems Ptracker gives more information like the chain between caller and called) and for some of them a product we developed to correlate CICS-Transactions with LINKed/CALLed programs (written to SM

Re: Tracking called (non-main) programs using SMF records

2019-11-13 Thread Mike Schwab
http://www.longpelaexpertise.com.au/ezine/SoftwareUsageWithoutTADz.php For many years IBMs Peter Relson has offered a free ‘as is, no warranty’ tool to monitor program fetch activity: the Module Fetch Monitor. Contact Peter directly at rel...@us.ibm.com. On Wed, Nov 13, 2019 at 10:07 AM Steff Gla

Re: Tracking called (non-main) programs using SMF records

2019-11-13 Thread Scott Barry
Consider solution P-Tracker (ESAi Group, developer: UBS-Hainer) for IBM z/OS software/application program invocation tracking for audit, compliance, asset-management. Link: http://www.esaigroup.com/products/ptracker.htm Scott Barry SBBWorks, Inc. On Wed, 13 Nov 2019 18:06:12 +0200, Steff Glad

Re: Tracking called (non-main) programs using SMF records

2019-11-13 Thread Gord Tomlin
On 2019-11-13 11:06, Steff Gladstone wrote: We would like to clean up our load libraries by deleting unused programs. Is there any way to use SMF data to track real-time usage of programs which are not main programs but are called by other programs? We were under the impression that only execu

Re: Tracking called (non-main) programs using SMF records

2019-11-13 Thread Salva Carrasco
My two cents: - Update every program to make a trace call. I'll prefer General tracking facility than Generic Trace. - http://www.longpelaexpertise.com.au/ezine/SoftwareUsageWithoutTADz.php -- For IBM-MAIN subscribe / signoff /

Re: Tracking called (non-main) programs using SMF records

2019-11-13 Thread Seymour J Metz
GTF -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Steff Gladstone Sent: Wednesday, November 13, 2019 11:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Tracking called (non-main) programs using

Re: Tracking called (non-main) programs using SMF records

2019-11-13 Thread Leonardo Vaz
Wednesday, November 13, 2019 8:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Tracking called (non-main) programs using SMF records We would like to clean up our load libraries by deleting unused programs. Is there any way to use SMF data to track real-time usage of programs which are not main p

Re: Tracking called (non-main) programs using SMF records

2019-11-13 Thread Charles Mills
2019 8:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Tracking called (non-main) programs using SMF records We would like to clean up our load libraries by deleting unused programs. Is there any way to use SMF data to track real-time usage of programs which are not main programs but are called by other pro

Tracking called (non-main) programs using SMF records

2019-11-13 Thread Steff Gladstone
We would like to clean up our load libraries by deleting unused programs. Is there any way to use SMF data to track real-time usage of programs which are not main programs but are called by other programs? We were under the impression that only executions of main programs (PGM=) were recorded w