Virtual IMS User Group Sponsors
Virtual IMS User Group | October 2024
Dynamically manage aspects of your IMS Connect environment without recycling IMS Connect
Divyam Bhatia
Product Developer
BMC Software
Divyam Bhatia, Product Developer
Divyam Bhatia is a Staff Product Developer at BMC Software. He is an experienced application delivery specialist with a demonstrated history of working in the information technology and services industry. He is skilled in IBM Mainframe Programming languages such as High Level Assembler and COBOL and has extensive experience debugging codes using XPEDITOR and dump analysis.
Read the Transcription
[00:00:00] – Amanda Hendley, Planet Mainframe
Welcome, everyone. Thanks for joining us. You should come in… muted. We just ask that you stay that way until it is time for Q&A, and then you could raise your hand, potentially to ask a question. Probably. We’re going to go ahead and get started so we give Divyam plenty of time. If we haven’t met, my My name is Amanda Henley. I’m your host for our virtual user group series, and today we are talking IMS. Thanks for joining us. We meet every other month, and we’re excited to have you here. This is going to be a great session.
[00:00:43] – Amanda Hendley, Planet Mainframe
For our agenda Today, we’ve got just a couple of introductory slides. We’ve got our presentation, Q&A. We’ll follow our presentation. We’ll have some news and articles for you to check out, and then we will talk about our next session. Today. Let’s get started.
[00:01:03] – Amanda Hendley, Planet Mainframe
After today’s session, I do want to ask that you complete the exit survey. It’s two questions. It’ll take 2 seconds when you leave. It’ll just pop up and ask you what you thought about today’s program.
[00:01:15] – Amanda Hendley, Planet Mainframe
I want to thank our partner, BMC, for sponsoring our virtual user group. They are a provider of innovative solutions that help to optimize performance security and modernization.
[00:01:31] – Amanda Hendley, Planet Mainframe
A little bit of news for us. Planet Mainframe just announced our new editor and producer for the Sheryl Watson Tuning Letter. We’re excited to have Mark Wilson on board. If you’re not familiar with the Tuning Letter, check it out. It’s an amazing resource. Subscribers get access to 8,500 pages of mainframe strategy and solutions and CPU charts. It’s a great hub of technical information about your mainframe. There are a ton of satisfied customers, and it is a subscription program.
[00:02:08] – Amanda Hendley, Planet Mainframe
You can see us plan a mainframe at IDUG EMEA in Valencia next week, and then I’ll be at GSE UK exhibiting, November 4 through 7. Hope to see you there. Without further ado, let’s get on to our session. Today, we’re talking about how to How to dynamically manage aspects of your IMS Connect environment without recycling IMS Connect. Divyam Bhatia is a product developer at BMC Software. He works on the AMI Energizer for IMS Connect. Program, primarily. With that, I’m going to stop my share so you can take yours over. You all just need to unmute. You’re muted.
[00:03:13] – Divyam Bhatia, Product Developer, BMC Software
Hello. I think he’s working. Am I audible now?
[00:03:16] – Amanda Hendley, Planet Mainframe
You’re audible. I don’t see your screen yet.
[00:03:18] – Divyam Bhatia, Product Developer, BMC Software
There we go. I’ve just shared it.
[00:03:21] – Amanda Hendley, Planet Mainframe
That’s okay. We have a ton of people. It’s hard for me to manage my screen. Let me go ahead and pin you so you can be there in spotlight. Okay. Well, thank you so much for presenting for us today.
[00:03:35] – Divyam Bhatia, Product Developer, BMC Software
Yeah. Thank you, Amanda, for giving me this opportunity to go about to present this. Yeah. Okay. Good morning, good afternoon, good evening to everyone. Today, we would be discussing on how to dynamically manage the aspects of the IMS Connect environment without recycling IMS Connect. Essentially, the This slide would be divided into major four sections.
[00:04:05] – Divyam Bhatia, Product Developer, BMC Software
I hope my slides are changing well. Let me choose on that. That’s great. The first topic that we would be discussing is how do messages get into and out of IMS and how do clients interact with IMS Connect itself. This will be covered under IMS Connect workflow. After that, we would be just creating and reloading exits, of course, without reloading the IMS Connect. How it is done, it is done via the Energizer product that BMC has. Then we have the other option of having a workload governor. We will discuss everything in detail. This is just a simple brief that I just wanted to give. The Energizer product does come with some UI interface as well. We would be discussing everything in detail now.
[00:04:58] – Divyam Bhatia, Product Developer, BMC Software
Before that, my basic simple introduction. I’m Divyam Bhatia, working as a product developer at BMC Software. If anyone wants to connect with me, these are my QR codes for the LinkedIn and Outlook. I hope we would be connected after this slide and PPT.
[00:05:18] – Divyam Bhatia, Product Developer, BMC Software
I’m just starting with the IMS Connect workflow just to give the components that we have. We have a client, we have this IMS Connect, we have the IMS and we have the MPR region, that is a message processing region in which the message processing program runs. Essentially, when we go ahead and start to send the messages, here the flow will start with the event ID0008, if you can see it in the MPRs section, which represents the start of the message processing region. That’s how it starts. Then we are ready to receive the messages from the client After that, the client will send the message via the TCP/IP port. You see this box near to this client. The message that IMS Connect will expect is, should start with a 4-by total message length, followed by the actual message that is the IRM header, IMS Request header. This is IMS Request Message header, essentially. Then we have the data segment. Once that happens, it reaches the Socket. The 3C event ID will tell me that it is preparing for Socket Read, and 49 event ID will tell me that the Socket Read has been done. After that, the message will enter the user message exit with the event ID of 3D. Each message that is received by IMS Connect is processed by a user message exit that you see this box. This routine will translate or format the messages so that it is in a format that is acceptable to IMS itself. Once that’s done, We move on. The read function is invoked through the user message exit. Once that’s done, the user message exit is returned through the event ID 3E. Essentially between this 3D and 3E, The message gets formatted into a IMS-readable format, not the client-readable format. Once that’s done, the message is sent to OTMA via the cross-coupling facility, XCF. You see this here, XCF-OTMA. After that, once the message enters the IMS, essentially, we would not be discussing this in detail because of the time. Once When the message enters, it enters to the IMS through event ID 1. After that, it enters the message queue with event ID 35. Then it goes through the MPR. There are different event IDs here, 560731. We will not be discussing this in detail. Our focus is once it comes back to the IMS Connect, how the messages are being processed. Once that’s done, it returns to the message queue via the event ID 3. Once that’s complete, it returns from the message queue into IMS with event ID 31. After that, it enters the IMS Connect region via the event ID 42. Forty-two represents message that was received from OTMA after the processing happens.
[00:08:50] – Divyam Bhatia, Product Developer, BMC Software
Once these messages are processed, IMS Connect will receive the messages through OTMA. That’s what we see in this box. Any transaction or any communication that happens between IMS Connect and IMS goes through the OTMA here. Once that’s done, the processed message will enter with event ID 3D into user message exit again. Because initially we had done this 3D and 3E read functions, the messages were formatted in a format where IMS can read it. Now, I’m When we are sending back this to the client, we would want it to be client-readable format. And hence, the user message exit will invoke the XMIT function that you see in this arrow. And once that’s done, the message will is done into a client-readable format, and it would be represented by the event ID 3e, that is user message, exit, return. Once that’s done, the formatted message or the processed message which is written back to the Socket through the event ID 4a. Once every functionality is complete in IMS Connect, we would send back the response to the client itself. This will be sent and the MPR that started with the event ID of 008 will shut down with the event ID of 007 after the whole processing is complete. I hope we are clear on this. If anyone has some questions, we can just discuss it in the QA itself. I hope that would be okay.
[00:10:44] – Divyam Bhatia, Product Developer, BMC Software
Moving on. Now, when we talk about IMS Connect, IMS Connect functions through exits, essentially the user message exit that we were seeing here. Essentially, when We are talking about exits. The exit should be written, as per IMS Connect, it should be written using assembler, which will require time, skills, also maintaining these exits, and If there are any system disruptions or some issues, the performance would be reduced. We need time, effort, expertise, skills, everything to upkeep these exits.
[00:11:26] – Divyam Bhatia, Product Developer, BMC Software
To solve that problem, the Energizer product Out, gives me an option of going ahead and using these interactive dialog boxes to create the exit. I will just briefly run through this. This is the virtual exit that I am trying to create. Here, we need to type in the virtual exit name, whatever name the user chooses. After that, we have some different options, Activate Message Routing for this exit, or Return a full word message length, allow Energizer extensions, post transaction expiration for all messages, Essentially, this will give me a freedom to go ahead and without actually writing the assembler quotes, I will just take this interactive dialog boxes, give the name, and the energiser will create it for me. This is one interactive dialog box that we were talking about. This is how we are going ahead and trying to manage things dynamically. Once that’s done, we do have some options for dynamically reloading the exits and processing options without recycling IMS Connect.
[00:12:38] – Divyam Bhatia, Product Developer, BMC Software
We can recycle customer exits, security exits, router options, exit configurations, and different things. These are all done through basic commands which the product has embedded in itself. It’s a very simple thing that we just need to go to the panel and get the command number and that will run. If not, we can simply go ahead and just type down the command and we will get the same results.
[00:13:07] – Divyam Bhatia, Product Developer, BMC Software
I would just be running through these commands one by one. These are very short commands, so I hope This will be okay. Here I’m trying to reload my customer exits. After any modifications that have been applied to the customer exit, the changes can be easily reloaded by using this command or typing in the option 10 on the Energizer panel. After that, we can reload security exits as well. Similarly, we will go about with option 11 or just typing down this command.
[00:13:43] – Divyam Bhatia, Product Developer, BMC Software
Once that’s done, Now, essentially, Energizer will provide me data store routing or routing simply. This will redirect the messages to the most suitable data store that is available for processing. This is done to attain the highest amount of efficiency and maximizing the performance and reducing any bottlenecks that we have. This can be done in two ways. As you can see in the slide, it is done through Affinity Manager, which identifies and directs message with distinct processing characteristics. Essentially, if a set of messages has certain characteristics of processing, it will be sent to the appropriate data store. Essentially, it forms the groups of characteristics, and according to that, it goes about and sends it to the appropriate data set. Then we have the load Balancer technique, wherein the messages are routed based on predefined weights within the chosen load balancing method. Essentially, say, for example, some message has a load of 100, it will be routed to some data store. If someone has 80, then it will be routed to some different data store. When we combine these two components, we essentially get the most efficient and most effective routing, and the messages are processed, as I said, to maximize performance and minimize bottlenecks.
[00:15:19] – Divyam Bhatia, Product Developer, BMC Software
These are the router options that we can reload using the simple command, reload options type router or by typing in option 8. We can also reload the exit configurations. Essentially, this is to reload virtual exits or customer exit for any message ID corrections or customer exit configuration changes. Any corrections that are done to message ID, customer exit configurations, or other components in the exit can be just simply reloaded, and we do not need to restart IMS Connect. This is done through option in the IMS Connect panel. Now, we do have some feature of having an e-group. This is a coupling facility that communicates between different address spaces, such as, say, MPR or the Icon address space or the IMS control region. This can be used to connect different type of data stores, different type of IMS Connects. We will just go through these in detail in the next slide.
[00:16:30] – Divyam Bhatia, Product Developer, BMC Software
Ims. Essentially, this is the one IMS Connect with multiple data store configurations. You have this blue box wherein we have the IMS Connect. The red one represents the e-group. Energizer runs within the IMS Connect, so essentially it is a part of IMS Connect. After that, this IMS Connect is connected to one, two, and three data store. Essentially, this is one IMS Connect which is connected with multiple data stores, one, two, and 3. This is one configuration. This is generally not used practically. These are simply used in some test environment or where we have very few data stores to manage, or we have just one single application used. We do not use multiple applications. In these cases, this can be used, although this is rarely used in the product. Now we have this IMS Connect in the same e-group. Again, just to represent, this is one IMS Connect, second IMS Connect, which runs within one e-group. This IMS Connect connects to two data stores, one and two. This IMS Connect connects to per data store. This is usually used We just have one single group, e-group to maintain. It is useful, but not practically useful that much. We do have this when we just have one single eGROUP. This is the most used one, multiple IMS Connects, wherein one IMS Connect is a part of one eGROUP and second IMS Connect is a part of second e-group. Similarly, they are connected to different data stores. A is connected with one and two in this case, B is connected to three and four in this case. This is usually used when you require different routing specifications. Say, for example, I need to go ahead and give one message to IMS Connect A, and I want it to be routed to data store 2. Second message I want to give to IMS Connect B and route it to data store 3. This is where it helps me because they are different e-groups, so I can just go about and decide it for me. Also, this is used where we have single system, that is a whole system, wherein we can have different characteristics of message routing. This This is how we reload the egroup options using option 7 or just simply typing in this command. We can also reload the IMS Connect options. Any changes into IMS Connect options can just simply be reloaded by this. You have this option of reload options type Connect ID. After that, we can reload ODBM configurations as well. If you change the ODBM options, you must reload the ODBM configuration member. That’s the requirement for the changes to take effect. This is usually done when we add or update a target alias, add or update PSP groups, add result groups, add alias routing, or activate ODBM routing.
[00:19:48] – Divyam Bhatia, Product Developer, BMC Software
These are the options that we have. Once that’s done, we just simply go ahead and reload this ODBM Configurations member by going about with option 10. Now, we did talk about some Workload Governor. Essentially, what does Workload Governor do and what is this panel all about? We would just be discussing it in detail. Energizer will reinforce transaction protection within the IMS system. This will shield against any overload and prevent any disruptions that might occur in an IMS system. The Workload Governor will allow me for precise control over the volume and frequency of the incoming messages on IMS Connect and efficiently prevent any potential outages that we have. In any case where these designed parameters, these designated parameters are surpassed, the IMS Connect will start to reject messages. This is most essential when we need to prevent outages by preventing any wrong applications or any run away transactions from overloading the system. Just to go about the screen. These are the governor options that we have. This is the transaction limit per second. How many transactions Incoming transactions can be handled per second. I have maximized this to 1,000. We can give any value. Warning threshold.
[00:21:24] – Divyam Bhatia, Product Developer, BMC Software
This is the percentage where the warning will be issued that, yes, the system is getting overloaded. We would be issuing some warnings. In this case, it would be 550% of 1,000. The cycle interval in which it should check whether the number of messages have exceeded is five seconds for me. Every five First again, it will keep checking that whether the total number of messages that have been received are more than 500. If it is more than 500, it will start to give me warnings. Once that’s done, we have low warning limit as well. We can set the low warning limit. Essentially, say I have set the transaction limit to 1,000 and low warning to 10. Below 10, it will again give me warnings that the number of messages are not appropriate. Then we have this granular governor option, which we write in the proclip member. We can granularly go ahead and control everything here. Essentially, that is not something that that we would be discussing in this presentation, but we do have some granular governor options as well. Apart from that, these are some options that we can activate. Essentially, they are not of much importance for this PPT or this presentation, so we can just simply skip that.
[00:22:52] – Divyam Bhatia, Product Developer, BMC Software
If you need more information on leveraging the load governor for availability and stability, you can scan this QR code. We have a BMC page or a channel wherein we upload these videos. You can go ahead and check these videos. This is essentially where we prevent problems from happening in the first place. Essentially, this is a stats summary that we have. If you just see the output of this command, this is the stats summary of the exit. We can identify the location of a problem, comprehend the transaction workflow, gather the data on peak loads by specifying trace record options, and analyze any statistical information that we have for transactions, exits, and data stores. I would I must be picking this one exit. This is my exit name. The current rate is zero. The messages per second received are zero. Peak was 0.20. Input Minimum messages were two. Input average is 489. Minimum messages that were received were 451, and maximum size of the message that was received was 528, and it processed with zero errors. Essentially, it will give me all the data for each and every exit. If any of my exit is going haywire, we can go ahead and check the stats and we can just narrow down on the problem.
[00:24:29] – Divyam Bhatia, Product Developer, BMC Software
Essentially, it will prevent any problems from happening in the first place if we keep monitoring these chats. If not, then the second option would be to go ahead and just simply check this and get to the root cause of the problem.
[00:24:46] – Divyam Bhatia, Product Developer, BMC Software
This is the UI part that we have for the Energizer. Essentially, this was done to accommodate more people into the product because a lot of people in the modern world do not really go about studying mainframe or liking mainframe. This is something that we came up with. If you just see this interface, we have added to the capabilities of IMS Connect with this UI. This can help us analyze any transaction workflow, create graphs, grids, et cetera, to help users better analyze and prevent any problems from occurring. This UI also comes with a discovery function which It helps in identifying which IMS Connect address space is up and running and accepting messages from the client. The green ones that you see here are active IMS Connects, and these are inactive. The green ones would be accepting messages from the client. These would not be accepting messages from the clients. That’s one thing to this.
[00:25:50] – Divyam Bhatia, Product Developer, BMC Software
Also, we have some basic details. What were the connect options? The name is SP5A icon. What are the eGROUP options? What are the e-link options? What was the user message exit, ODBM options, routing options, and what IMS was using at that time.
[00:26:08] – Divyam Bhatia, Product Developer, BMC Software
Essentially, if we go about and click the other IMS Connect, we will see the same information based on the output of that IMS. Help panels were integrated at every part of this UI. This helps with detailed help section, which helps the users to get more information and It helps the users not to switch between mainframe screens and the IBM documentations. We have all integrated into this. It’s one roof and you have all the solutions here. You can just go about and see the help sections, and this will help the users to go ahead and identify any problems here. We have the section of Execute Commands. Essentially, if you see this is the Active IMS I can execute the commands, also the commands that we saw on the mainframe screen, just a few slides back. This is simply a point and shoot drop-downs menu. There is a video that I would play so that we do have the clarity on this.
[00:27:23] – Divyam Bhatia, Product Developer, BMC Software
Here, if you see, I’m just simply selecting the Command section and selecting the display. We have set and list as well. After that, I’m just simply selecting a keyword group. Once we execute that, you see the output here. Here you also have the option of re-executing the command, copying the data, what was the time and date that this command was run. Also, if you choose to clear this, you can clear this. If not, then you can also to see what were the commands that were run on this icon and just check on the outputs again. Essentially, with mainframes, usually we cannot see the previous outputs. This will add a feature to see my previous output if I choose not to clear out the screen. Moving on. We can fetch trace records as well. We can fetch transaction trace, event trace, energize the command trace, history trace, statistics trace. This is the output of a transaction trace, which has a sequence number, client ID, user ID, exit, data store, transaction name, and the date At the same time, this was run. This is usually important when we need to check on the statistics and see, for example, some transactions have come to the icon but haven’t been processed.
[00:28:57] – Divyam Bhatia, Product Developer, BMC Software
We can go about and check this. Again, a simple video of the UI. Just I want to show this. We go to this Trace section. We click on Fetch Trace Records. Here you see it will give me options of having transaction trace, event trace, or any other trace. It will help me select date and time. Once that’s done, we click on Apply and we see the output. Essentially, it is the same output that we saw previously. I would not be going ahead and explaining this. We do have one more option here of searching based on the fields. Say, for example, I want to search this client ID that ends with 208. I can simply type 208 and everything that has a client ID of 208 will be displayed here. That’s one more strong feature that we have. Also, you can see the details here. I just simply clicked one of the trace, and I see this message from client, message from IMS, message sent to client, trace records, etc. Results, data store routing. Also, you can just see the sequence number of that transaction as well. You see this IMS request message header. What were the details?
[00:30:31] – Divyam Bhatia, Product Developer, BMC Software
Ims request message header, the detailed view for that. Simply scrolling down to see what information do we get. You have This is actual message from the client itself. Also, we can see the message that was from the IMS, actual message, message sent to client, trace records, exit results, data store routing. You have all the information present on the UI as well. Moving on. This is the most important in the prominent section on this console, wherein the users are provided with a visual representation of energizers message processing. In the event of any system issues, this tab will help me and enable me to proactively mitigate any potential problems that were there. This is also a video. I would just play it around and we can discuss that. We go to the statistics tab and here we get some options. Transaction summary, detest to summary, exit summary. We click on Exit Summary. Here you can see the graphs that we have, message count based on message count, message size, and message rate. You see 100 input messages were there, 100 output messages were there. This was a part of Java Exit. After that, 100 reads were invoked, 100 exits were invoked.
[00:32:08] – Divyam Bhatia, Product Developer, BMC Software
You also have this other exit of sample 0, and you see the total of all these. Also, you can see the message size here. Based on the message size, you have the graph. Input average was 528. Input maximum was 528. Input minimum was 528. Then you can see the output as well. Output average was 372. Then you have based on message rate as well. The peak was 2.8 on the Java exit. If you see, it peaked at three on all the exits. You also see the grid format to this as well. If someone wants to see the grid format, number of errors, response time, date time, peak input rate, peak output You can simply go about and see everything and you have other options as well. These are simple options and you can just see the charts or the grid format for both of them. If you want to just look into the new user interface, we have more options on the YouTube channel. You can just simply go about and scan this QR. It will land you to the same page. Last, we move on to the Q&A section. So any questions, any doubts, anything that anyone wants to add, it is greatly welcome.
[00:33:55] – Amanda Hendley, Planet Mainframe
Thank you. Everyone, you’re welcome to put your Q&A into the chat. Or if you’d like to come off of mute and ask a question directly, that is also fine. We’ll give that a couple of minutes. Alan is asking about the transaction limit and is wondering if you can talk about that being a per IMS Connect instance or data store.
[00:35:02] – Divyam Bhatia, Product Developer, BMC Software
I think this doubt was about the governor section. Am I correct, Alan? Yeah. Okay. Essentially, it is regarding the one instance that we have for the IMS Connect. Brad is asking, what is the official name of the BMC product presented today? It is BMC AMI Energizer for IMS Connect. If you want, I can just type that as well in the chat. Thanks, Joan.
[00:36:22] – Amanda Hendley, Planet Mainframe
I had a question that you, I believe, touched on a little bit, but if someone is assessing the addition of this, what are some of those key factors they really need to focus on to justify a transition?
[00:36:41] – Divyam Bhatia, Product Developer, BMC Software
Could you come again on the question? I did not really get the question.
[00:36:47] – Amanda Hendley, Planet Mainframe
If someone is considering adopting this tool, what are the key factors that they need to consider to justify it?
[00:36:58] – Divyam Bhatia, Product Developer, BMC Software
Essentially, as I said, that this product will run inside the IMS Connect itself. It is not a competition or a replacement to any product. It is just enhancing the capabilities of an already existing product. If you are keen to manage your IMS Connect dynamically, that is one point to that. The second point to that is usually with IMS Connect, we see if we go about and make any changes, we have to go ahead and completely restart the system with the product that we are talking about today. We essentially don’t need it. It’s just a simple run a command and just reload the IMS Connect the address space and it is good to go. Essentially, if you ask me what are the factors that contribute to this product or what are the factors someone should consider? If you’re keen at managing your IMS Connect space dynamically, this is the go-to product for Thank you. Yeah.
[00:38:07] – Amanda Hendley, Planet Mainframe
Alan asked about many-to-many configuration.
[00:38:12] – Divyam Bhatia, Product Developer, BMC Software
Yes, you can have many-to-many or any combinations. As John mentioned, IMS Connect is pretty flexible on that. It essentially means you can have any configurations as per the user. Brad asked one question. So, energizer can replace the direct writing of IMS Connect assembler exits. Essentially, yes, Brad. It is not saying that we are replacing writing exits. Still, you have the option of writing your own exits. If not, Energizer will provide you with the powerful tool to you go ahead and have virtual exits in your system. Essentially, you will have two exits. One is the customer exit and one is the virtual exit. If you are nice to say the assembler itself, so We can just go ahead and write a virtual exit and it will help me to go ahead and without writing any assembler code, I can just have it with me.
[00:39:51] – Amanda Hendley, Planet Mainframe
Any other questions? All right. Well, if anyone has anything that you all want to pop up before we leave today, you can go ahead and put that in there. But Divyam, I want to thank you for your presentation today on this tool. Always great to hear about new I’m going to go ahead and share my screen again, if I can find the correct button. There we go. As I mentioned earlier, we’re going to have this video and the transcript and presentation available for access on our virtualusergroups.com website. You can pull it there and rewatch it later. Before we go, here’s a couple of links for you.
[00:41:09] – Amanda Hendley, Planet Mainframe
Alan, we’ll get to your question, I promise.
[00:41:11] – Amanda Hendley, Planet Mainframe
A couple of links for you, a link for the BMC AMI tool. I found an article about moving from IMS to DB2 that I thought was interesting from Craig Mullen’s. I want to do a shout out to for Planet Mainframe. If you are interested in writing or a contributor. We take more than written articles. We love to get other content, like video or first-person perspective or technical briefs. We’d love to talk to you about publishing with Planet Mainframe.
[00:41:47] – Amanda Hendley, Planet Mainframe
Divyam, did you want to see that comment or question about reload options?
[00:41:54] – Divyam Bhatia, Product Developer, BMC Software
Sorry, I was on mute. Just a second. I did not see the question. I would not be sure. Maybe John can take up this question. My initial understanding would be a yes.
[00:42:18] – John O’Dowd, BMC Software
Yeah, this is the security exit that you use. I believe so. I haven’t worked the product in a long time, so I’m not… But Alan, we can get back to you on that if you like and let you know on that. But my initial thought is, yes, I believe that is correct. If we’re talking about the exit in particular, and that’s what I think you’re talking about, I believe so. As far as reloading the options, we can reload any of our options. That’s That’s not an issue. If you’re changing things related to that, yeah, security exit. That’s what I thought. We’ll have to get back to you, Alan, on that and let you know for sure. Honestly, I can’t remember off the top of my head. I’m sorry about that. We reload all of the exits that we can. I don’t believe from my memory, it serves me correctly. I don’t believe we left any of them that could not be reloaded. I believe the answer is yes. Okay?
[00:43:41] – Divyam Bhatia, Product Developer, BMC Software
Thanks, John.
[00:43:44] – Amanda Hendley, Planet Mainframe
I did put up ways to get involved and connect with Planet Mainframe from our different social media channels. Most of you are, but make sure you’re also subscribed to our newsletter for the virtual user groups, and that’ll let you know when videos are available as well as our next sessions. With that, we are done for today. I’d love to get you… Let me get you the date for our next session so that we will see you in two months on December 10th. So thank you, everyone. Alan, do you want to drop… You can direct message, but do you want to drop your contact information in so we can get you that answer?
[00:44:41] – John O’Dowd, BMC Software
Yeah, thanks, Amanda. That’s what I was going to ask him. Or you could just send it to me direct. Oh, that’s great. Got it, Alan.
[00:44:50] – Amanda Hendley, Planet Mainframe
Thank you, Alan.
[00:44:51] – John O’Dowd, BMC Software
I’ll answer you later today. Okay?
[00:44:53] – Amanda Hendley, Planet Mainframe
All right, great. Well, Devyam, thank you so much. Thank you, everyone, for hopping on today, and John, for your help, too.
[00:45:03] – Divyam Bhatia, Product Developer, BMC Software
All right. You have great- Thanks, Amanda.
[00:45:06] – John O’Dowd, BMC Software
We appreciate it. Thank you, Amanda, for hosting us.
[00:45:09] – Amanda Hendley, Planet Mainframe
Thank you.
[00:45:11] – Divyam Bhatia, Product Developer, BMC Software
Bye-bye. Bye-bye.
Upcoming Virtual IMS Meetings
December 10, 2024
Virtual IMS User Group Meeting
Understanding What IMS Applications Can Do and How You Can Benefit From REST APIS
February 11, 2025
Virtual IMS User Group Meeting
IMS Catalog implementation using Ansible Playbooks
Sahil Gupta and Santosh Belgaonkar
BMC