|
View previous topic :: View next topic
|
| Author |
Message |
MasahideSouma
New User
Joined: 23 Apr 2024
Posts: 3
Location: Japan
|
|
|
|
Hi. This is my first post.
How can I save SYSLOG as text data via PCOMM in the 3287 printer definition?
I remember that over 20 years ago in the data center, a 6262 printer was continuously outputting SYSLOG.
I'm thinking it would be convenient if such a thing could be done in tk4-, where SYSLOG is output in the \log folder.
| Code: |
| [SYSLOG]--->>[VTAM]-->>[TN3270]---->>>>[PCOMM/printer]-->>SYSLOG(text file, streaming data) |
Looking at the SYSLOG output of tk4-, it seems to be directly defined as a printer in \conf\tk4.cnf.
However, I think this is a feature of Hercules.
| Quote: |
| 030E 1403 log/hardcopy.log ${TK4CRLF} |
Is this possible?
Thank you. |
|
| Back to top |
|
 |
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
|
|
You might look at using the WRITE LOG command to save it to a dataset periodically.
Or possibly the External Writer XWTR |
|
| Back to top |
|
|
MasahideSouma
New User
Joined: 23 Apr 2024
Posts: 3
Location: Japan
|
|
|
|
Thank you.
I know "Write Log" "SDSF PT" "XWTR"
I want to forward SYSLOG to file servers, etc., with as little impact on z/OS as possible. Near real-time.
(by hardcopy console printer. can you understand?? Any ideas? )
I’m Japanese and not good at English. Waiting for your response.
regards |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
| Back to top |
|
|
MasahideSouma
New User
Joined: 23 Apr 2024
Posts: 3
Location: Japan
|
|
|
|
Thank you. However, unfortunately, the URL you introduced does not seem to be a solution for z/OS.
I found a manual for OSA-ICC, so I might understand if I read this.
publibz.boulder.ibm.com/epubs/pdf/ioa2dp00.pdf
I will read it a little and think about it. |
|
| Back to top |
|
|
|
|
