Update each member with a call rexx_monitor directly after the /* rexx */

:)

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Lizette Koehler
> Sent: Wednesday, September 14, 2016 10:37 AM
> To: [email protected]
> Subject: Re: Capture REXX/CLIST software usage.
> 
> What problem are you trying to solve.
> 
> The more you monitor the slower it can get.
> 
> Are you trying to identify who is using what?
> 
> Are you trying to identify who is a consumer of resources?
> 
> ??
> 
> Lizette
> 
> 
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]]
> > On Behalf Of Massimo Biancucci
> > Sent: Wednesday, September 14, 2016 3:05 AM
> > To: [email protected]
> > Subject: Capture REXX/CLIST software usage.
> >
> > Hi everybody,
> >
> > I'm wondering what's (if it's reasonable) the best way to capture
> > usage of REXX/CLIST member.
> >
> > For LOAD member it's possible to "monitor" some SVC and capture the
> > information (like TADz).
> >
> > I've tried to run a simple JCL:
> >
> > //ST003    EXEC  PGM=IKJEFT01
> > //SYSPROC  DD DSN=myexec,DISP=SHR
> > //SYSTSPRT DD SYSOUT=*
> > //SYSPRINT DD SYSOUT=*
> > //SYSTSIN  DD *
> >  %TEST
> > /*
> >
> > and capture with a GTF all the SVCs called.
> >
> > I'm expecting at least a BLDL but nothing.
> >
> > The goal is to know what piece of software are used and, in a
> > statistic way, clean the libraries from unused software,
> >
> > Any idea ?
> >
> > Thanks a lot for your support.
> > Massimo
> >
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to