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 see about crafting a share requirement if you think it might be
useful. Or perhaps SNMP or MIB or API for other products. But I think that
direction maybe a bigger performance hit.
I am sure IBM is going to warn against performance issues with something
like that. So I would think a warning in using WTO might be appropriate.
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vernooij, CP (SPLXM) - KLM
> Sent: Tuesday, October 21, 2014 7:41 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Question on WRITE statements in ACS and Automation
>
> 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 AFAIK, it is not possible. Any change in
this
> would be welcome.
>
> Kees.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Tidy, David (D)
> Sent: 21 October, 2014 16:32
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Question on WRITE statements in ACS and Automation
>
> 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 ( JOBNAME = 'DFSKERN' )
> REVISE("Y" AUTOMATE)
>
> Then I activate a message table that triggers an exec to write each
message it sees
> from the jobname to a global variable stem (incrementing an index), and
> asynchronously pick up the output later.
>
> Of course in your case, the message table processing could be much
simpler, and
> permanent (I only do the set-up to retrieve the data I have triggered, and
undo it
> afterwards).
>
> Best regards,
> David Tidy
> IS Technical Management/SAP-Mf Dow Benelux
> B.V.
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lizette Koehler
> Sent: 9 July 2013 15:00
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Question on WRITE statements in ACS and Automation
>
> 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 automation
> product, OPS/MVS, AFOPER, Tivoli, and action the message?
>
> If a user is creating a dataset and using an invalid DSN, I could put a
> write statement in the code that says
>
> WRITE MYACS001I Invalid DSN for the storage group requested.
>
> Then if it went to SYSLOG I could capture it and send an email to the
> storage team for review.
>
> Or if my user was requesting way to much space for a specify storage pool,
I
> could do something similar.
>
>
> So, it would be nice, in my opinion, to be able to create an event
> notification that an automation tool could capture and then perform some
> action (i.e. email the storage team)
>
> I understand that I can redirect to a different pool and provide other
> actions within ACS code.
>
> But since a lot of logging goes directly to the DFHSM logs or SYSOUT DDs,
I
> have to have someone manually review to identify what is going on.
>
>
> Another example, there is an ARC0019I message that indicates the CELLS are
> too small for DFHSM. It is only in the SYSOUT DDs. I will be opening a
> SHARE requirement to be able to redirect these types of messages to SYSLOG
> so that an automation tool can send a notification to the storage team.
>
>
>
> The only way I see of doing it is to filter the output of the task to find
> the ACS code WRITE statements or filter the DFHSM SYSOUT DDs.
>
>
> Any thoughts are welcome. And if you have any other messages or functions
> in DFHSM that might need redirection, let me know.
>
> Thanks
>
> Lizette
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
