I was being a smart-arse.
Who would've guessed that? But how do we do all that?
I'll bet that we have 100 iSeries companies here in central Iowa. But
all I hear is that iSeries people are "impossible" to find. A good
friend of mine has been looking for an Admin job for nearly two years
and finally just found a 30 day temp contract. (I'll admit that he
wasn't looking that hard... but nobody was looking for him.)
We have a dozen WebSphere developers here that wouldn't touch an iSeries
to save their life. In fact they'd rather use WSAD at $1100 per seat
than use WDSC for free! (No Additional Charge(tm)) Yet they use iSeries
data all the time via JDBC and MQ Series. We run WebSphere on Linux.
Both run on iSeries. But IBM and our BP sold the business on Linux on
Z, now we've migrated to Intel Linux to cut costs.
Shortly after the iSeries rebranding I was asked to rewrite my job
description. My job description for an iSeries Administrator was then
rejected by HR because "No one knows what an iSeries Administrator is."
We run all of our imaging on System i, but when we went looking for a
new imaging system IBM sold management on CM on Windows, because it was
"more compatible" with Outlook (which insists on changing my System I to
uppercase!) Maybe it was the other way around. I don't know, I wasn't
invited to that meeting.
All I'm saying is that we need to do the simple things first. I'm happy
to support rebranding, give me a name I can use! And then keep it!
Regards,
Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company
-----Original Message-----
From: Trevor Perry [
mailto:trevor@xxxxxxxxxx]
Sent: Thursday, June 07, 2007 8:49 AM
To: Midrange Systems Technical Discussion
Subject: Re: MSFT video demos Host Integration Server
Scott,
I was being a smart-arse. When I said " Why can't we look for "System i
developers with AS/400 skills", I meant that we SHOULD start looking for
them. The more we write that on job descriptions, the more people put
that on their resumes, the more we will become a System i brand.
We already had the discussion about Google, etc..
Trevor
On 6/7/07 9:38 AM, "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> wrote:
Cause ya can't find 'em. Google is not a friend to the System i. (Or
was not previously. It seems to be much more i friendly today.) In
past searches for System i Google would search for "System" and ignore
the "i". "AS/400" was just as bad, the slash would get ignored and
you would find all manner of pages with "AS" and "400" in them. Hence
the plethora of "AS400" jobs.
Who knew that there was a highway in California called I5?
www.ihoz.com/I5.html
I'm sure that the members of some committee within IBM get paid a lot
of money to develop these names, but after all these name changes
couldn't someone have suggested something a little more search engine
friendly?
Or don't those people use the internet?
I'm confidant that there is a world market for at least five System
i's, but we've already got ours, we need to sell them to someone new.
Regards,
Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company
-----Original Message-----
From: Trevor Perry [mailto:trevor@xxxxxxxxxx]
Sent: Wednesday, June 06, 2007 7:10 PM
To: Midrange Systems Technical Discussion
Subject: Re: MSFT video demos Host Integration Server
Walden,
It is true that the present is mired with the names of our heritage.
And sure, when looking for people who can work on System i, we must
recognize that most of them will have AS/400 on their resume. Why
can't we look for "System i developers with AS/400 skills"??
Trevor
-----------------------------------------
DISCLAIMER:
This message and accompanying documents are covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and
contains information intended for the specified individual(s) only.
This information is confidential. If you are not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, copying, or
the taking of any action based on the contents of this information
is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail, and delete the
original message.
midrange.com
