The Synon 2E and Plex Emporium by Lee Dare (A developer blog)
A blog devoted to Broadcom 2e (CA 2E, Synon 2E) and Plex. Serving the Plex2E community with knowledge sharing for nearly two decades. Coding tips, Standards masterclass and 'how to' guides. A cool place to hang out and bookmark for some of the best Synon content on the web.
Saturday, December 6, 2025
Synon 2E Internals - Steve Hinzmann Synon User Group 1991
Useful synon sites
Synon 2E related useful sites and links
Synon 2E - Technical Deep Dives
Synon 2E - Technical Deep Dives
Synon 2E - SQL and Model files summary
Synon 2E - SQL and Model files summary
Friday, December 5, 2025
Synon 2E - Standards posts all in one page
Synon 2E - Standards posts all in one page
Tuesday, November 18, 2025
The Worst Word in the Workplace
I wrote a post about the word 'resource' many years ago.
https://leedare-plex2e.blogspot.com/2016/10/feeling-resourcefulnot.html
Today for a little bit of fun, I asked 'co-pilot' to refactor it, add humour and energy. This was the result! Quite impressive if you ask me.
Thanks for reading and don't bother reading the original as 'Co-pilot' did way better!
Lee.
Let’s get one thing straight: my most hated word at work is not f$%k, tosser, w&^%er, or even the dreaded “c-word” (and no, I don’t mean Christmas). Those are fine in context — usually shouted across a pub table after someone’s nicked your chips.
The word that makes me twitch, the one that should be banished from every office, is this:
Resource.
“We don’t have the resource.” “I’ll check the resource schedule.”
Every time I hear it, a little part of my soul packs its bags and heads for the door.
Why “Resource” Is Rubbish
Calling people “resources” is corporate code for: you’re replaceable, interchangeable, and about as personal as a stapler.
Once upon a time, companies had Personnel Departments — actual humans looking after actual humans. Then came the Americanisation: Human Resources. That was the moment we stopped being people with skills and started being reference numbers with salary ceilings.
And if your company still talks about you as a “resource”? Time to polish your CV, or at least stand up and say: No thanks, I’m not coal.
People ≠ Commodities
Let’s remember what a resource really is: coal, sugar, soybeans, oil, cocoa, tin, steel. All fine words for things you can burn, melt, or trade on an exchange.
But last time I checked:
Coal hasn’t written a single C# function.
Sugar hasn’t debugged a parsing algorithm.
Soybeans haven’t offered counselling.
Oil hasn’t built a school.
Humans do those things. Humans with talent, experience, and the kind of domain knowledge you can’t just order off Amazon Prime.
The IT Angle
I work in software engineering. Sure, you need technical chops — databases, languages, platforms. But you also need business knowledge, context, and the ability to translate messy real-world problems into clean code.
Thinking you can pluck someone off the street and have them instantly productive on a complex system? That’s not “resource planning.” That’s fantasy football.
Better Words Exist
Open a thesaurus and you’ll find words that actually respect people:
Ability
Capability
Talent
These words recognise skill. They acknowledge contribution. They don’t reduce you to a consumable item that can be replenished like printer paper.
My Crusade
Project managers love “resource.” Middle managers (especially the 6ft 5” ones with clipboards) practically bathe in it. But every time I hear it, I cringe.
So I’ve made it my mission: wherever I work, I beat the drum to eradicate this corporate cancer. Replace it with Capability, Skills, Staffing, Talent, Capacity — anything that reminds us we’re humans, not coal.
Final Word
If you’re reading this and still calling your colleagues “resources,” stop. Unless you genuinely believe Dave from Accounts is interchangeable with a sack of soybeans.
Words matter. Use better ones.
Moan over.
Thanks for reading,
Lee.
Sunday, March 23, 2025
Google was hiding the site
Thursday, April 4, 2024
Did you know Synon 2E has a Full Screen Mode?

If I remember rightly, the command key used to bring up a window and you could chose between Basic (might have been intermediate) and Advanced mode. This has long since been removed from the o/s and the command key merely acts as a toggle nowadays. The reward of course was the ability to see more of your processes and interactive sessions.
Here is my current 'Pro' setup lol.

A lesser-known scenario and also a bit harder to remember all the options, is the ability to extend the records shown when viewing a model list.
So how do you set these values?
From the main Services Menu take option 11 for Edit model profile (YEDTMDLPRF) or as the menu implies, execute the command. Then set the options accordingly.
Sunday, March 17, 2024
They say a picture is a 1000 words!
Anyhow, a colleague was talking about tag clouds the other day and it got me thinking.
"What would this blogs labels look like in a tag cloud?"
So......... I popped online and googled for a tag cloud generator and discovered this site that looked pretty good.
https://simplewordcloud.com/ or you can click here: Simple Word Cloud Generator
I excitedly 'cut n pasted' it into the input field on the website and clicked the button.
Wednesday, March 6, 2024
Synon 2E Understanding CONstant usages
As a side, IMHO there should be next to no CON usages in a well architected model apart from, values like *BLANK, 0.00 and some tolerance towards values like 12 (months), 52 (weeks), 365 (days), 100 (percentage). I'd even accept 1,2,3, 9999999 etc.
I draw the line at meaningful literals that could have been scoped conditions (CND) or database values.
My main reason for this is that there isn't a way (via the 2E tool interface) to check for usages of CON values. Obviously, we can scan the generated source, but then what about all the genuine field names or comments.
Back with 2E! When generating the source, it somehow lets the generator knows about them and adds them into the code (inline) or as part of a data structure. Take a look at the bottom of a source listing if you don't believe me.
Here is a sample function using some constants. Note the 'Create Flatfile' call is passing in 'FLAT FILE CoNsTANT' as CON.
Followed by the structure of CON values at the bottom. Note: Sometimes the CON is generated 'inline' at the point of the MOVE.

It looks like we have some constants referred to in field ELMTTL ** (Element Title - highlighted RED). This could be a good start but there are some obvious limitations. Whilst it looks like it covers basic *MOVE and *CONCAT field assignments, when we have hardcoded values going into a function call (PURPLE), the CON value isn't reflected in the ELMTTL field.
However, it looks like 2E maintains a surrogate reference for each unique CON value used in the AD regardless of AD syntax used. (GREEN)
So, all that is left for us to do is to identify the CON values we want to analyse, work out what functions they are linked to via the AD code and some pretty cool impact analysis is before us.
Here is a sample SQL retrieving the many different usages of the term 'constant'. As CON is only ever associated with field @@SUB3, the query is quite straight forward.
Ensuring you have the correct library list.
This query returns unique records for each of the functions using CON context with the word 'constant', the UPPER() function ensures we don't miss any based-on case differences. The rest of the query does a basic join to return some additional fields from YMDLOBJRFP (This is the *ALLOBJ or *A model list). You can add to this query or tidy up names and formatting however you like.
Thanks for reading.
Lee.












