●● IRC: #techbytes @ Techrights IRC Network: Saturday, October 11, 2025 ●● ● Oct 11 [03:38] *GNUmoon2 has quit (connection closed) [03:38] *GNUmoon2 (~GNUmoon@i9qtak2d2eia6.irc) has joined #techbytes [03:46] *GNUmoon2 has quit (connection closed) ● Oct 11 [06:57] *GNUmoon2 (~GNUmoon@kskf72fm7sp7y.irc) has joined #techbytes [06:57] schestowitz[TR2] https://www.thelayoff.com/t/1k779yxj8 [06:57] schestowitz[TR2] " [06:57] schestowitz[TR2] @OP, the jury is still out on the advantages of adopting the cloud model. Financial institutions require stability and backward compatibility. So. don't count mainframe, AIX on Power as dead. [06:57] schestowitz[TR2] 2 hours ago by Anonymous [06:57] schestowitz[TR2] | no reactions | Reply [06:57] schestowitz[TR2] Post ID: @cd+1k779yxj8 [06:57] schestowitz[TR2] +2 [06:57] schestowitz[TR2] The post reads that they moved to SAP S/4 Hana on AWS - a packaged software solution that does not require re-coding antiquated Cobol/CICS (legacy) languages to modern languages. Since CBA was already running SAP on the Mainframe, the only work required was to migrate the data to databases running on AWS and then pointing the SAP software to those AWS datasources. This type of SAP-to-SAP-on-cloud migration has been going on at majo [06:57] schestowitz[TR2] r (and smaller) companies for decades. IBM Consulting has had numerous clients that have done this. I've worked on 2 of these projects and heard of at least 3 others in the past 15 years. [06:57] schestowitz[TR2] Also this post suggests that the bank expects to retire their mainframe in 18-month - however, there is nothing in the news stories to back this up. Rather, it says that the Migration Project lasted 18 months from early 2024 to Sept 2025). CBA still has Credit Card Transaction Processing running on their Mainframes. While they may be able to scale back their MF footprint, it is not completely going away. [06:57] schestowitz[TR2] 8 hours ago by Anonymous [06:57] schestowitz[TR2] | 2 reactions (+2/-0) | Reply [06:57] schestowitz[TR2] Post ID: @b6+1k779yxj8 [06:57] schestowitz[TR2] -3 [06:57] schestowitz[TR2] Lots of customers have tried to move off the mainframe and miserably failed. There are even more customers that are just totally afraid of even trying. Good for IBM! [06:57] schestowitz[TR2] 11 hours ago by Anonymous [06:57] schestowitz[TR2] | 9 reactions (+3/-6) | Reply [06:57] schestowitz[TR2] Post ID: @ar+1k779yxj8 [06:57] schestowitz[TR2] +2 [06:57] schestowitz[TR2] @a3 The first migration is always the hardest because there is always the potential for unknown and unseen "gotchas". But then successive migrations can go smoother than the first, and there will be lessons learned from the first one and each successive migration. There is no gain without some pain. [06:57] schestowitz[TR2] I'm still waiting to read that Red Hat migrates VMWare VMs without too much effort. Hopefully in this lifetime... [06:57] schestowitz[TR2] 11 hours ago by Anonymous [06:57] schestowitz[TR2] | 2 reactions (+2/-0) | Reply [06:57] schestowitz[TR2] Post ID: @an+1k779yxj8 [06:57] schestowitz[TR2] +5 [06:57] schestowitz[TR2] First of all, congratulations to the bank. @a3 does raise a good point but it's more of an IBM article of faith than the real argument. @OP, to maybe dig a bit deeper into @a3's point, do you have details such as: what were they using (DB2, IMS, DFSORT, CICS, ....)?; how much code did they have?; all COBOL?; probably most importantly, how long did the transition take and how big was the team that did it? [06:57] schestowitz[TR2] A lot of customers would love nothing more than to get off the mainframe. But, of course, they are terrified by @a3's argument. A couple of things might help. Success stories such as Commonwealth Bank. Also, the migration effort is likely to find not so good code that can be made better as part of the migration. They could get better code that runs faster. [06:57] schestowitz[TR2] 12 hours ago by Anonymous [06:57] schestowitz[TR2] | 5 reactions (+5/-0) | Reply [06:57] schestowitz[TR2] Post ID: @aj+1k779yxj8 [06:57] schestowitz[TR2] +6 [06:57] schestowitz[TR2] "The argument for keeping the mainframe has always been it's crucial for high transaction high security environments" [06:57] schestowitz[TR2] No, the real argument has always been it costs a fortune to migrate and there's no guarantee the migration will be successful because of the 30+ years of undocumented legacy code accumulated. [06:57] schestowitz[TR2] " ● Oct 11 [07:05] *croissant_ is now known as croissant [07:11] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [07:32] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Oct 11 [10:36] *x-amarsh04 has quit (Quit: Konversation terminated!) [10:40] *x-amarsh04 (~amarsh04@kpkpy434dfgzc.irc) has joined #techbytes ● Oct 11 [12:07] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [12:30] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Oct 11 [13:10] *psydroid3 (~psydroid@36imbvshpgubk.irc) has joined #techbytes ● Oct 11 [17:36] schestowitz[TR2] https://www.thelayoff.com/t/1k77r9dqd [17:36] -TechBytesBot/#techbytes- ( status 403 @ https://www.thelayoff.com/t/1k77r9dqd ) [17:36] schestowitz[TR2] " [17:36] schestowitz[TR2] I was as guilty as anyone. Most people in IBM have bees in their bonnets. It never takes long to figure out what grinds whose gears. Whenever I wanted to steer the conversation away from where it was heading, I would drop in a "of course, issue X will need to be considered." That would light up someone and burn some meeting time. Top tip: to ki-l off most of the meeting, ask the most senior person there to explain his or her pet pe [17:36] schestowitz[TR2] eve. [17:36] schestowitz[TR2] Over the years, the name of the annual review process changed a number of times. I'll use PBC because that name was used for a while. Never once on a PBC did I (or anyone else) claim greatness for helping to make IBM meetings useful or productive. Never once did I (or anyone else) receive management feedback in the other direction. Also, in the annual employee satisfaction survey, there were occasional comments about questioning th [17:36] schestowitz[TR2] e necessity of some meetings but I don't really recall comments about the molasses in which most meetings were held. [17:36] schestowitz[TR2] Effective meeting chairing and effective meeting participation isn't on anyone's Think-40 list. No one wants to talk about it because another failed meeting is a shared failure. That leaves us with a situation where pointless meetings are part of the scenery and everyone just accepts it and gets on with their real jobs, In addition, calling meetings is seen as taking positive action; the more the better. [17:36] schestowitz[TR2] " ● Oct 11 [18:10] schestowitz[TR2] "Im turning 41, but I dont feel like celebrating. [18:10] schestowitz[TR2] Our generation is running out of time to save Word Documents to a local drive. [18:10] schestowitz[TR2] What was once the promise of a .DOC file conveniently located on our hard drive is being turned into the ultimate tool of control. [18:10] schestowitz[TR2] Once-free countries are introducing dystopian measures such as Save to OneDrive. [18:10] schestowitz[TR2] Germany is persecuting anyone who dares to save Word Documents to offline storage. The UK is imprisoning thousands for backing up to USB sticks. France is criminally investigating developers of LibreOffice. [18:10] schestowitz[TR2] A dark, dystopian world is approaching fast while were asleep. Our generation risks going down in history as the last one that had local storage and allowed it to be taken away. [18:10] schestowitz[TR2] Weve been fed a lie. [18:10] schestowitz[TR2] By betraying the legacy of our ancestors, weve set ourselves on a path toward self-destruction a total loss of Word Docs on our local drives. [18:10] schestowitz[TR2] So no, Im not going to celebrate today. Im running out of time. WE are running out of time." ● Oct 11 [20:41] schestowitz[TR2] "Volunteer Moderators and Code of Conduct Committee Members are among the most powerful people in any computer related organization (gaming, open source, etc.). [20:41] schestowitz[TR2] - Unelected. [20:41] schestowitz[TR2] - Little to no oversight. [20:41] schestowitz[TR2] - Massive administrative and censorship power. [20:41] schestowitz[TR2] They can squash any discussion, ban any member, and fundamentally change the makeup of an organization. [20:41] schestowitz[TR2] Abuse of these roles is one of the primary strategies of Leftist Activists within the computer industry." ● Oct 11 [21:07] *x-amarsh04 has quit (Quit: Konversation terminated!) [21:11] *x-amarsh04 (~amarsh04@kpkpy434dfgzc.irc) has joined #techbytes ● Oct 11 [22:45] *psydroid3 has quit (Quit: KVIrc 5.2.6 Quasar http://www.kvirc.net/)