Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
David Spiegel... I have my presentation PDF. Send me your email address and I'll forward it to you. My email: wayn...@gmail.com On Tue, Mar 26, 2024 at 12:06 AM David Spiegel < 0468385049d1-dmarc-requ...@listserv.ua.edu> wrote: > Hi Tom, > I logged in with SHARE Userid/Password before asking the question. > > Regards, > David > > On 2024-03-25 08:29, Tom Marchant wrote: > > SHARE proceedings are available to SHARE members only. Log in with your > SHARE user ID. > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
David, I'll see if I have my original presentation. I can send it off list. Regards, Wayne On Tue, Mar 26, 2024 at 12:06 AM David Spiegel < 0468385049d1-dmarc-requ...@listserv.ua.edu> wrote: > Hi Tom, > I logged in with SHARE Userid/Password before asking the question. > > Regards, > David > > On 2024-03-25 08:29, Tom Marchant wrote: > > SHARE proceedings are available to SHARE members only. Log in with your > SHARE user ID. > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
Hi Tom, I logged in with SHARE Userid/Password before asking the question. Regards, David On 2024-03-25 08:29, Tom Marchant wrote: SHARE proceedings are available to SHARE members only. Log in with your SHARE user ID. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
SHARE proceedings are available to SHARE members only. Log in with your SHARE user ID. -- Tom Marchant On Mon, 25 Mar 2024 06:53:47 -0400, David Spiegel wrote: >Hi Wayne, >I followed the link and saw the description. >How do I access the content? > >Thanks and regards, >David > >On 2024-03-25 01:26, Wayne Bickerdike wrote: >> Tom Longfellow. >> >> I presented a session at Share in Phoenix in 2019 on the subject of CICS >> transactions written in REXX. >> >> https://www.share.org/Events/Past-Events/Proceedings/Proceeding-Details/cics-and-rexx-some-useful-tips-and-tricks >> >> The capability has been around for years. Just happens that nobody bothers >> to install the feature (unless it's me, LOL). >> >> >> >> >> On Fri, Mar 22, 2024 at 6:35 AM Sri Hari Kolusu wrote: >> > I see a lot more research in my future. >>> Tom, >>> >>> Here is something to get you started. >>> >>> https://www.ibm.com/docs/en/cics-ts/beta?topic=server-rexxcics-commands >>> >>> Thanks, >>> Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
Hi Wayne, I followed the link and saw the description. How do I access the content? Thanks and regards, David On 2024-03-25 01:26, Wayne Bickerdike wrote: Tom Longfellow. I presented a session at Share in Phoenix in 2019 on the subject of CICS transactions written in REXX. https://www.share.org/Events/Past-Events/Proceedings/Proceeding-Details/cics-and-rexx-some-useful-tips-and-tricks The capability has been around for years. Just happens that nobody bothers to install the feature (unless it's me, LOL). On Fri, Mar 22, 2024 at 6:35 AM Sri Hari Kolusu wrote: I see a lot more research in my future. Tom, Here is something to get you started. https://www.ibm.com/docs/en/cics-ts/beta?topic=server-rexxcics-commands Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
Tom Longfellow. I presented a session at Share in Phoenix in 2019 on the subject of CICS transactions written in REXX. https://www.share.org/Events/Past-Events/Proceedings/Proceeding-Details/cics-and-rexx-some-useful-tips-and-tricks The capability has been around for years. Just happens that nobody bothers to install the feature (unless it's me, LOL). On Fri, Mar 22, 2024 at 6:35 AM Sri Hari Kolusu wrote: > >> I see a lot more research in my future. > > Tom, > > Here is something to get you started. > > https://www.ibm.com/docs/en/cics-ts/beta?topic=server-rexxcics-commands > > Thanks, > Kolusu > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
>> I see a lot more research in my future. Tom, Here is something to get you started. https://www.ibm.com/docs/en/cics-ts/beta?topic=server-rexxcics-commands Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
CICS transactions written in REXXMind blown! I see a lot more research in my future -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
The “night light” CICS program can be quite simple and written in any language — in REXX, for example. You probably ought to include a link to the replacement application and help desk details. For example: REPLACEMENT APPLICATION NOTICE [Application ABC] replaced [Application XYZ] on March 8, 2024. To access the new application please visit: https://www.ourcompany.com/abc-app If you need special assistance with this transition please contact Our Company Help Desk at 1-800-555-1234 and use QuikHelp code RAN24AA. Press or to return to the previous screen. — Timothy Sipples Senior Architect Digital Assets, Industry Solutions, and Cybersecurity IBM Z/LinuxONE, Asia-Pacific sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
Tom, I think whoever is responsible for this project is going to have to come up with some help around the CICS stuff. It sounds like Solve is similar to CL/Supersession. I don't think the Solve software will help you much in this situation. Technically the CICS program does not need a MAP to send out the message. It can do a simple EXEC CICS SEND (without the MAP option) of a text message to the screen with the needed information and then the program would end. Then in CICS you would point the transaction that is being decommissioned to this simple program. If you wanted to get tricky you could put in code to see what transaction is calling the program and customize the message based on the transaction. If it was me, I would just keep the program simple and use a single generic message. Paul -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: Wednesday, March 20, 2024 4:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS Here is a set of CICS transactions to perform DogeCoin transactions via CICS. The first screen could be simplified to be display only, https://github.com/mainframed/DOGECICS On Wed, Mar 20, 2024 at 4:01 PM Tom Longfellow <03e29b607131-dmarc-requ...@listserv.ua.edu> wrote: > > Paul > > The answer to your question is BOTH - Individual apps are being yanked before > the eventual complete shutdown of everything the region does. > > Our internal thoughts parallel your ideas for CICS. One of the hurdles is > that since the mainframe is marked for death, we have no real access to > application programmers to write the new transaction. I am too old to learn > all the skills required to write the code and screen maps for a new program. > > Solve is a VTAM session switcher. If we ever get a dedicated region with > only the "landing page" transaction, I would redirect SOLVE to send the > switching definition to the 'death zone' CICS. > > Has anybody developed an 'Out of Service' transaction for use during periods > of extended application or data base maintenance? > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
Here is a set of CICS transactions to perform DogeCoin transactions via CICS. The first screen could be simplified to be display only, https://github.com/mainframed/DOGECICS On Wed, Mar 20, 2024 at 4:01 PM Tom Longfellow <03e29b607131-dmarc-requ...@listserv.ua.edu> wrote: > > Paul > > The answer to your question is BOTH - Individual apps are being yanked before > the eventual complete shutdown of everything the region does. > > Our internal thoughts parallel your ideas for CICS. One of the hurdles is > that since the mainframe is marked for death, we have no real access to > application programmers to write the new transaction. I am too old to learn > all the skills required to write the code and screen maps for a new program. > > Solve is a VTAM session switcher. If we ever get a dedicated region with > only the "landing page" transaction, I would redirect SOLVE to send the > switching definition to the 'death zone' CICS. > > Has anybody developed an 'Out of Service' transaction for use during periods > of extended application or data base maintenance? > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
It’s been decades since I wrote my last CICS application, but if I understand your desire, you want feedback better than an IBM error. If transaction ABCD previously pointed to a program (with maps and everything associated) it’s trivial to create a page that says “Nobody home, go away.” or maybe more like the transaction requested has been decommissioned. Then point to that. Granted, there are a few details, but is that what you want? Also, I’m thinking of a Tn3270 screen. If some GUI apps are calling CICS, that’s a bit different. I retired as we were moving away from the mainframe, but that’s some of what we did. R Sent from [Proton Mail](https://proton.me/mail/home) for iOS On Wed, Mar 20, 2024 at 5:01 PM, Tom Longfellow <[03e29b607131-dmarc-requ...@listserv.ua.edu](mailto:On Wed, Mar 20, 2024 at 5:01 PM, Tom Longfellow < wrote: > Paul > > The answer to your question is BOTH - Individual apps are being yanked before > the eventual complete shutdown of everything the region does. > > Our internal thoughts parallel your ideas for CICS. One of the hurdles is > that since the mainframe is marked for death, we have no real access to > application programmers to write the new transaction. I am too old to learn > all the skills required to write the code and screen maps for a new program. > > Solve is a VTAM session switcher. If we ever get a dedicated region with only > the "landing page" transaction, I would redirect SOLVE to send the switching > definition to the 'death zone' CICS. > > Has anybody developed an 'Out of Service' transaction for use during periods > of extended application or data base maintenance? > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
Paul The answer to your question is BOTH - Individual apps are being yanked before the eventual complete shutdown of everything the region does. Our internal thoughts parallel your ideas for CICS. One of the hurdles is that since the mainframe is marked for death, we have no real access to application programmers to write the new transaction. I am too old to learn all the skills required to write the code and screen maps for a new program. Solve is a VTAM session switcher. If we ever get a dedicated region with only the "landing page" transaction, I would redirect SOLVE to send the switching definition to the 'death zone' CICS. Has anybody developed an 'Out of Service' transaction for use during periods of extended application or data base maintenance? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS
Hi Tom.. Let me start by saying I don't know anything about Solve. Now to my question. Are you talking about individual CICS transactions going away or are you talking about the whole CICS region going away? If you are talking about individual CICS transactions then you could handle things in the following way. Have someone write a simple CICS program that sends out a screen with the needed information. Then you could point the transaction that is going away to that simple program. If you are talking the whole CICS region going away then I'm not sure what you could do within Solve. I guess if the CICS region only supported one transaction and you used Solve to logon the person to that region and then automatically launched the transaction you could use my suggestion about. Paul -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Longfellow Sent: Wednesday, March 20, 2024 11:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Ideas for less-distruptive disruptions - Netmaster:Solve and CICS Our mainframe is scheduled for termination.As such, bits and pieces are being turned off. Management edicts wants "no sudden surprise screens and error messages" when a function is killed. A "landing screen" has been proposed that would do the required hand holding with messages like "Thanks for playing" "This is gone" "Call someone who cares" and maybe "Counselors are on call for your withdrawal needs" I am scrambling for ways to implement this to kill one thing and replace it with another things that is not dead (yet).. The SOLVE product is basically a session switcher that takes your 3270 terminal to another active VTAM application. I am wondering if there is a way to change the menu item on the switching screen to replace it with the "landing screen". For example, it currently connects you to a CICS region. Is there something else it could do within Solve to just blast them "landing screen" when they select the menu item? I am not a CICS programmer I just start and stop CICS regions. I am picturing some kind of 3270 based transaction that could just present the "landing screen" and nothing else. I would then replace my current welcome menu with this new transaction. Ending this transaction could even be used to initiate a sign off from CICS. Anybody have ideas on how to get from here to there and allow this mainframe to die politely and with dignity. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
