Taking the night off so here are some cartoons.




Oh wait a minute! Maybe I'll write sumpin' for the computer geeks.
We got our new processor in on Monday and I've been working on the hardware configuration since Wednesday. I need to move four systems off the old processor and onto the new one. I have to make this as transparent to the users as possible. I'm creating the IODF (I/O Definition File) and drawing cabling diagrams. Operations started laying the first cables this afternoon.
<EsotericSysprogStuff> I'm gonna have to do most of the network stuff since our network guy has DKS (Doesn't Know Shit) Syndrome. I asked him to do some research. We use a lot of OSA (Open Systems Architecture) Adapters and the z/900 now supports OSA Express. I had been told that with OSA Express you do not need the OSASF (OSA Support Facility) to configure the adapters. I asked the network guy to research this for me and find out if it were true. He sent me softcopy of the forkin' books. I didn't ask him to send me the forkin' books but to find out the forkin' answer. I found another resource who told me that what I had heard was true. I know I should have gone to the other resource first, but I'm trying to force the network guy to actually learn sumpin'.
Last week I moved some Canadian systems to another processor so we could shut down the processor those systems were on and move it out the door. We couldn't get the RSCS/NJE (SNA file transfer stuff) links to work so we assigned that problem to the network guy. This was actually a joke by my team lead and myself since we knew there was no way he was gonna figger it out. Our VM guy, who does the RSCS stuff, sent the network guy the failing VTAM message to help him figger it out. Now the VM guy was in on the joke also since we knew the VTAM message (which he is supposed to know) would be beyond his comprehension. Anyway the VM guy told me that we were missing a CDRSC on his VM VTAM and should we have the network guy code it. I said the dipstick doesn't even know what a CDRSC is and I would code it on Monday. </EsotericSysprogStuff>
So why do we have an incompetent network guy? This is a legacy of my ex-CDSMŽ (Clueless Dipshit Manager). The new network guy was told he was gonna be the network guy a full year before the old network guy retired. He drug his feet on getting up to speed until after my team lead told my ex-CDSMŽ many times that this guy would not be ready. So about three months before the old network guy retired, my ex-CDSMŽ told the new network guy he was it and had better start preparing. Not enough time. So guess who has to do most of the troubleshooting for network failures? Yep. Me.
Over the past week as I've been trying to figger out the best way to make the network changes (It's gotta be me since we need to get this stuff done.) I've been mumbling over and over, "I wish Bill (the old network guy) were here." My team lead has even gone to our financial guy and asked if we could bring Bill back on contract to do the network move. Nope.
So next week we should have our first test system up on the new processor. I'm hoping to have the first system moved to the new processor with all the OSA stuff done for that system the following week. I'm gonna have to set up some VTAM CTC's (Forget the network guy. Like many of you reading this, he doesn't know what I'm talking about either. ) Then before I move the next system I'll have to decide what to do about the CMC's and start recoding the NCP gens.
As an aside here, the reason I get away with a lot of the crap I do at work is because I know and can do a lot of shit that no one else can. My team lead realizes this and he has told me that as long as I do what he asks he will protect me from myself. That is a monumental chore, but I actually have been behaving myself for the last two years. I can retire anytime I want. The end of my career is in sight. Management is not gonna waste any money on me in the form of raises or promotions so there is no incentive for me to bust my ass. This is a mistake on their part since with the proper motivation I could be twice as productive as I am.
No one ever said management had to be smart.
Off to bed. G'night!
Posted by denny at May 21, 2004 08:43 PMKeep that Big Iron and give me midrange!
Posted by: Sailor in the Desert on May 22, 2004 02:03 AMI really hope your co-workers don't ever stumble across this site. The amount of low self esteem suicides that would result could bankrupt your employer.
Posted by: Bill, The Radioactive Monk on May 22, 2004 08:41 AMThe duck's methods seem fair to me!! ;)
Posted by: Indigo on May 22, 2004 11:41 AMSailor in the Desert - Midrange processors are still considered mainframes. The two teams with the highest customer sat at my site are large systems and AS/400. The lowest customer sat belongs to workstation support.
Bill - Actually some of my co-workers do read my stuff. My friend Brian is one and he always gets on me for using fuck too much. The competent ones aren't offended and the incompetent ones are so fucking stupid they would not recognize themselves. Management would think I was writing about another company.
Posted by: Denny Wilson on May 22, 2004 12:25 PMI have been away from the AS/400 community since 1998. Though, there are still some hardcore big iron folks that will contend only 390's are mainframes. Have you ever been to a COMMON Conference?
Sailor
Posted by: Sailor in the Desert on May 22, 2004 11:52 PMNope, I never have. Our AS/400 person used to be VM so I consider her and her AS/400 stuff mainframes.
Posted by: Denny Wilson on May 23, 2004 07:43 PM