I suspect that this it is possible to trap these messages with System
Automation 3.4 which has a new function: Joblog Monitoring - Messages produced
by an application and written to the Joblog or a spooled data set but not
WTO'ed to syslog can be made available for automation. We use this to
Hi Lizette,
Just cleaning up some mails, and I came across this.
There is a message revision table in Netview that could be used. I have used it
in a temporary way when I issue a command from system automation that only
generates ouput in a joblog - in my case the revision table is:
UPON (
David,
I think the problem with the ACS WRITE statements is, that the output does not
travel the route that can be intercepted by your solution. It goes directly to
the JES2 Message file of the job. I have been looking too for a way to collect
these message and have them emailed to me, but
Hi Kees,
Sorry - yes you are right. I was thinking that I was rerouting joblog ouptut,
but in fact I am just trapping syslog output that is not normally passed to
automation.
Best regards,
David Tidy
IS Technical Management/SAP-Mf
Dow Benelux B.V.
I think I would need a WTO process for ACS code rather than a WRITE
statement. Or in addition to a write statement.
So for those sections of ACS code I might want to have
IF DSN = SYS1.** Then
Do
Write Restricted HLQ HLQ
WTO mymsgid Job JOB Tried to use DSN
EXIT
END
I will
Darth Keller wrote:
Well, this gets more interesting as it appears that there must be some
automation in place as I'm only seeing the IGD010*I (* = 07, 08, 09, 10) on
2 of my 4 production LPAR's.
More reasons for a SHARE requirement!
Are you sure your messages are not being suppressed?
I
I have a friend who is at z/OS V1.13
He asked me an interesting question that I am thinking of opening a Share
requirement on. Let me know what you think
When you create ACS code you can put WRITE statements into the process for
clarification. Is it possible to capture those WRITEs in an
I do see some of my SMS Write output in my syslog:
IGD01007I
IGD01008I
IGD01010I
But it appears that these are all from batch jobs. I tested allocating a
ds from my TSO session the WRITEs came back to me but are not in the
log.
ddk
This e-mail message and all attachments
Lizette Koehler wrote:
When you create ACS code you can put WRITE statements into the process for
clarification. Is it possible to capture those WRITEs in an automation
product, OPS/MVS, AFOPER, Tivoli, and action the message?
AFAIK, those WRITES are NOT written to SYSLOG. I have now tested
If people want these WRITE messages going to SYSLOG and put in a SHARE
request for that functionality, __PLEASE__ ask that it be optional. I get
enough crap messages on my z/OS SYSLOG as it is. To the point that I write
them to a data set which I then send to my Linux desktop simply so that I
can
Darth Keller wrote:
I do see some of my SMS Write output in my syslog:
IGD01007I
What magic trick did you do? Mine (from DATACLAS) in my batch job does NOT
appears in the SYSLOG!
Groete / Greetings
Elardus Engelbrecht
--
For
Well, this gets more interesting as it appears that there must be some
automation in place as I'm only seeing the IGD010*I (* = 07, 08, 09,
10) on 2 of my 4 production LPAR's.
Are you sure your messages are not being suppressed?
I still think the SHARE requirement would be valid as I want to
John McKown,
In any of my Share requirements, I always ask for a parm addition. Let the
current behavior be as it is, and for those that want the new function,
supply a new parm.
I understand completely about not wanting more entries in syslog or other
places.
Lizette
-Original
I've done some more testing and it doesn't look like I'm seeing messages
from all my batch jobs either. It looks more like dynamic allocations
some temporary datasets - which might also be dynamically allocated.
ddk
From: Darth Keller/WBY/ASSURANT/US
To: IBM Mainframe Discussion
14 matches
Mail list logo
