Thomas Traynor
Worked for 44 years on multiple systems. Comfortable with ZOS, Z/VSE, windows, UNIX, Chrome and Linux. Worked as developer and support, team lead and business analyst. COBOL, ASSEMBLER, BASIC, C, learning RUST & PYTHON. Developer and DBA using IDMS based applications, dev & support for DB2 based systems. I'm still learning and a semi-cranky senior!
Upcoming Linux tasks.
Downloaded and made a bootable USB with the latest #mxlinux. Old laptop backed up and ready to convert.
I have to try out the new version and then how well WINE works and for one of the online games I play. If it all goes well the laptop will be upgraded from Windows 10 to #mxlinux
Another thing that was drilled into me decades ago, repeatedly! I say the same thing to every new member of our team...
THERE ARE NO DUMB QUESTIONS.
If you don't know or are unsure, ASK!
Do not assume, ASK!
I will be so glad when the members are back from leave and we get the new person up-to-speed. Multiple Impact Assessments for several Change Requests and Request For Change. Regular on-call tasks. Forty-eight (and count) security requests. Multiple questions on several subjects for the system.
I AM NOT APOLOGIZING to anyone about the speed I am working at after ten hours of work (and at least four more to go). I have a triage list and if you are not in the top sixteen items on the list you will have to wait until everything is done or the boss of my boss changes my priorities. One body doing the work of what should be done by four and was originally done by seven.
I automated as much as we can, but there is a limit on how much we can do there.
One half a bottle of whisky left and may have to make a quick run for more if the workload stays the same.
Oh joy, great start to my work week.
Sole person for the week doing all tasks. I started at 05:15 and zero issues. Around 08:20 it went into the electronic septic tank. Ten to fifteen minute response time for anything that needed the network.
I did what I know we would be asked. I rebooted the system. Didn't work, and I let the team know through our chat that they may have issues too. Called helpdesk and it took ten minutes for them to remote to my machine. Determined it is a major network outage (no kidding, I knew that) and opened a ticket. Since Outlook depends on the network drive nothing has shown up.
Just watching my email and zero emails and I know the tsunami will hit eventually. I am not looking forward to that as I am the sole person on the team this week and will get flooded by system access requests, messages about the network, the oncall person and in the middle of prep work for an upcoming code release.
I DON'T HAVE ENOUGH WHISKEY to handle today and on the third large mug of coffee.