|
View previous topic :: View next topic
|
| Author |
Message |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Our site doesn't have SDSF, and I've never worked for one that does, so I'm not all that familiar with the product. However, I've seen a few posts recently that talk about retrieving data from the active SYSLOG using SDSF? Is this really a possibility? I haven't seen any other products that can do that. If so, I might have to make a recommendation to the company for us to consider obtaining it. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
| superk wrote: |
| Our site doesn't have SDSF, and I've never worked for one that does, so I'm not all that familiar with the product. However, I've seen a few posts recently that talk about retrieving data from the active SYSLOG using SDSF? Is this really a possibility? I haven't seen any other products that can do that. If so, I might have to make a recommendation to the company for us to consider obtaining it. |
An MVS without SDSF? How can that be?
BTW, nice avitar, does she have a sister? |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
Our office offloads SYSLOG daily and writes the contents to GDG files. Sure they migrate to Level 2, but if want to see what happened on a particular time and date, it is there to peruse.
You can also preallocate a dataset (like FBA/133/27930). Then go into the active SYSLOG (by entering LOG in SDSF).
On the command line, enter each command one a time:
PRINT ODSN 'HLQ.DATA.SET'
PRINT
PRINT CLOSE
If you want to place only part of the SYSLOG into the dataset, the 2nd PRINT may be coded:
PRINT 40 180 (to capture only lines 40 through 180) |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Our site doesn't have SDSF, and I've never worked for one that does |
Interesting. . . After a couple hundred mvs-type systems, i've never seen one that did not have sdsf - some places severly restrict access to it, but i've always found it on the system.
Typically, it is option "S" from the main ispf menu. Once in sdsf entering "log" will directly attach syslog. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Nope. Always (and I mean ALWAYS) has been either IOF or CA-Sysview. Never SDSF, at least as far back as I can remember. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
The reason I'm asking is that we have times when a user wants to issue a system command, which is not usually a problem. The problem is that they have no way to see the results of that command once it's been issued. Of course, right now we use Automation to handle these tasks, since it can see the responses as they come across the console.
CA-Sysview, which we have, won't let you do anything more than just browse the SYSLOG. There's no function to actually retrieve data from the SYSLOG. It's only allowed for data residing in the JES Spool. |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
| cpuhawg wrote: |
If you want to place only part of the SYSLOG into the dataset, the 2nd PRINT may be coded:
PRINT 40 180 (to capture only lines 40 through 180) |
You may also select a date/time range for print in SDSF using
PRINT [mm/dd/yy] hh.mm.ss [mm/dd/yy] hh.mm.ss
The dates are optional when specifying the to/from time range. |
|
| Back to top |
|
|
|
|
