Something we have done as the grunts (because we WANT to know if a product of value is soon to expire) is to set up automation (ops/mvs for example) to look for and email such soon-to-expire occurrences to we grunts - who then scream to our managers to scream to our contracts team to get the license paid
Thank You, Chris Hoelscher| ITI . DB Services . Mainframe Database | Humana Inc.| T 502.476.2538 or 502.407.7266 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Sunday, June 30, 2019 7:57 PM To: [email protected] Subject: Re: [IBM-MAIN] WTO for message that will require explicit deletion? @Peter, thanks. Frankly, the documentation of the more esoteric aspects of WTO seems haphazard to this observer. I think WTO's clarity of documentation suffers from the various things that have been layered on over the years such as MCS. As I wrote in the OP, the idea that DESC=3 requires an explicit delete comes from this in the doc: "If the task can determine when the operator has performed the action, the task should issue a DOM macro to delete the message." That is not logically the same as the statement "the message will hang out until it is explicitly deleted" but for better or worse that is what I inferred. An automatic DOM at step termination will preclude this approach for me, but does make logical sense and as you say is consistent with how MVS tends to do things. I intend to run an experiment with -- purely as an experimental hack -- a one minute or so delay before the jobstep task ends -- just for my own curiosity. OTOH, there is this: "When using the LINKAGE=BRANCH parameter, the system does not automatically delete a WTO issued by a caller in SRB mode. A caller in SRB mode must issue the DOM macro to explicitly delete any action message when the calling program ends." That would appear to be an approach that would cause a message to "hang out" past end of jobstep. Not sayin' it's a good idea, just sayin'. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Relson Sent: Sunday, June 30, 2019 4:36 PM To: [email protected] Subject: Re: WTO for message that will require explicit deletion? Charles, You started with <snip> I have an APF-authorized batch program that I want to have WTO a message that will hang out at the bottom of the console screen until it is explicitly deleted </snip> I'm quite sure that the system will automatically DOM a message upon termination of the jobstep of the issuer. That should not be much of a surprise. I'd hope it is mentioned somewhere (for completeness, not suggesting that it's at all obvious). That might be thought not to violate your requirement unless you added "and not cleaned up at step termination". Not all that many things fall into the category of "not cleaned up at step termination". Obtaining of common storage, of course, is one. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
