Re: the words "DO NOT CLOSE DOWN THIS APPLICATION"
Read again, I never wrote I didn't appreciate it, but that feature is never in the original scope.
3908 publicly visible posts • joined 15 Aug 2018
This doesn't seem to be a problem caused by "mainframe" or "ICL", but by poor design/architecture and lack of improvements spanning decades. The people in charge would have screwed it up if it was running on any platform, I would guess.
On a positive note, those screw-ups have been pensioned of by now and are reaping the rewards of their labour (underpayment of their pensions) ;)
Yup once you transliterate Restaurant into Cyrillic you get the Russian. Lots of Russian words are like that, there’s heap of Latinate/German loanwords in Russian. Crack the Cyrillic and they leap out at you.
And most of the maritime idiom is derived from Dutch (a result of Peter the Great spending time in the Netherlands).
Since closing velocities between orbiting stuff are potentially very high -- if things want to stay in orbit, they have to move very fast -- roughly 8km/s -- even small objects are potentially capable of punching right through anything they hit.
While theoretically true, but things in the same orbit move in the same direction and with the same speed. Problems only occur when things are in crossing orbits and only if the things are both*) at the crossing point of the orbits at the same time.
*)A three (or more) way collision is theoretically possible, but so unlikely I will leave it to the theorists.
If you write your code properly, you know what variables you use and why. This is not a crapshoot, developers do not generally declare variables without a reason.
Depends, on the AS/400 the compilers just pull in all fields from the used files, so an AS/400 program without unused variables is pretty rare.
Prof Peter Ladkin (Bielefeld/Abnormal Distribution)
The moral of the story is make sure your bosses boss is in the room when you throw the grenade.
A friend of mine (not in IT) used the nucleair option. As her final act before logging off and leaving the building for the last time she sent a carefully prepared farewell email to the entire company with all C-levels by name in the To: field. From a colleague, who lasted two weeks longer, she later learned that all managers in line above her for at least three levels were demoted for gross incompetence. A couple of months later the whole department was moved to another country.
There may be a one-in-a-million people who rise to management after having lived in helldesk, but this is more than an exception ; it's a miracle.
For helldesk you are completely correct, but I know of enough programmers and analysts that have risen to management and higher. The advantage is that they know IT, the disadvantage is that you can't baffle them with the end product of an uncastrated, adult, male head of cattle (aka rose fertilizer).
Here in NL, first Monday of the month at 12:00 sharp! never had a misfire AFAIK...
In that case you are not old enough, I still remember the occasional silence on the first Monday of the month (disregarding holydays like Easter and Pentacost) and also hearing them at other days/times without cause.
Really? Any large, multi-user, database worth running is worth protecting with a journal which is written to with a complete list of changes as they are made so that they can be rolled back or forwards as necessary. This is not a new invention, the ICL Data Dictionary System I worked on in the 1980's had it.
True, but journaling doesn't protect against dropping tables or even complete databases.
Actually at least 30 minutes before she is told her services are no longer required and if she is showing signs of heading for the door or serious issues arising even earlier. Don't leave a window of opportunity.
Depends a bit on the person. I've been told more than once that my services weren't required anymore (in one case twice at the same company) and I had full access up until the minute I logged off prior to leaving for the last time. At the company where I was employed twice (over ten years with a four month break after about three years) I could get QSECOFR access on the development machine in about four minutes, on the production machine it would have taken me a bit longer. I never abused that and I was informed of my contract being terminated well over a month in advance. There is something called professional pride.
On a side note: to convert an AS/400*) into a smoking pile of trash you only need QSYSOPR access and knowledge of a couple of basic commands.
*) or iSeries or however IBM likes to call it this month
If I read this correctly, the complaint is that the vehicle did not ascend inside a specified imaginary tube, but strayed outside it for 2 minutes.
In combination with "SpaceShipTwo was simply not climbing steeply enough.", I'd say a bit more tail wind (or less head wind) than calculated.