ehesive and more up-to-date information.
Profiling the SYSLOGs
We are using the JES repository feature and usually have 4 days worth of SYSLOG online; The current day's SYSLOG is on spool, and the three previous days' SYSLOG is on flat-DASD, but soft-indexed through the repository.
We maintain the contents of the JES repository, through automation; so I normally don't have to be concerned with managing its contents.
Lately, however, some of our PD guys have been manually "ADDing" older SYSLOG archives to the Repository; mostly to review some unresolved problems, using the filtering and zooming features of NetResults/z.
My question is this; How can I determine the DSNs of the data sets they have ADDed to the repository, so that I can manually DELete them, if and when the PD guys forget to do it ?
Good question. Probably one of the most frequently asked questions since the advent of the JES Repository feature, in release 3.4 of NetResults/390.
As you no doubt already know; the Profile SYSLOG (PS) function, by default, displays both "unspun" Spool-resident SYSLOGs, and Repository-resident SYSLOGs.
The Spool-resident SYSLOGs are identified by "Sn" under the "Log#" heading on the screen display; the Repository-resident SYSLOGs are identified by "Rn".
The remainder of the PS display basically provides the same kind of info that the other types of Profile requests (PN; Profile Netlog, PA; Profile AOlog, PR; Profile RODM log) do; that is, From/To dates/times of the messages contained on each log and the number of records on each SYSLOG. It does "not", however, provide the DSNs of the Repository entries.
To see the DSNs of the SYSLOGs in the Repository, you have to specify the "REPOS" operand on your "PS" request.
So, the answer to your question is:
Issue "PS REPOS" and you'll get back a slightly different Profile display that contains the Repository SYSLOGs "and" their corresponding DSNs.