There is quite a myth out there that IBM i is the machine of the SMB market. Well that is true in terms of IBM's definition of SMB which are companies with over 50 employees and annual sales well in excess of $30 million.
There are some well known large corporate accounts that support their franchises with turnkey packages that run on IBM i. There are also huge companies with field offices that have a machine in every field office. When you see quotes from vendors or partners about the number of small Power Systems IBM ships with IBM i it is very likely to a company that has a small IBM i based system in every store, warehouse, factory, car dealership, agent's office, etc.
The truth is that IBM has targeted mid-size companies for the AS/400. Additionally the vast majority of these customers primary software is a solution purchased from an independent software vendor and not software developed in-house by the company's IT organization.
Many of these companies who have 1500 or more machines (one in every business location) are looking to lower cost alternatives including Intel based systems (Windows or Linux), variations of Unix (SunOS, HP-UX, BSD, or other variation) . Some companies are looking at cloud based solutions. The bottom line is that a huge part of the IBM i install base had been location based systems. As companies migrate to lower cost solutions this will have a major negative impact on IBM and its revenue from IBM i on Power.
Going to need your help here, it occurred to me that we don’t have a plan for backing up those Vendor Schedules we turned into pdf’s on the DLS a while back. QDLS is easy but IFS, well same thing really without the restricted dos naming but finding them is a bit more humpty than finding your folder in the QDLS.
Can you either help me on what command I can use on IBMi to review folders with vendor looking documents in them or as I should have access to the network, any clues on a path that should work ?
Here is my email reply - remember this is all very much IMHO - Neatly copy/pasted into this blog in case it helps anyone else out there in IBM-i-land:
So this is a technique that I discovered while trying to get WDSSC220.127.116.11 working with the April 2013 build of Turnover V100 Windows Client. This works but I wouldn't recommend it as this is a much simpler solution. Well.. while we are waiting for Unicom to release a backward compatible plugins selection for Turnover V100. Assuming they ever will of course :(
If you absolutely must have the latest iteration of the standard Turnover V100 client - then you could try this. I wouldn't recommend this technique as it is blending both versions, but it does work. Use at your own risk.
But wait we can trick it into working with our old WDSC install. It's fairly straightforward but a little fiddly:
Install the latest V100 Client
Replace the Plugins from this new V100 client with the *older* ones
Tada! It works lovely... maybe... try at your own risk :)
If you are seeing compatibility errors, perspective crashes or white screen of death when trying to open Turnover from within WDSC then this might just help. I've had a horrible time trying to get WDSC7 Turnover Perspective working when using the latest download of the Turnover Client.
I finally figured out a simple way of fixing it (detailed here) and also discovered a more complicated and dirty way of getting it to work (at the bottom but not recommended)
If you install the latest 2013 version of the Turnover Client - you will soon find it does not support the old WDSC7. It seems that it supports the newer IBM Rational Developer product line, and compatibility with WDSC has ben rudely thrown in the trash.
Boris the Landrover is once again proving that it can refuse to start in nearly every State in the USA...
What makes it worse is that last Friday - I just got it back from the Garage who happily told me the problem was fixed. "A new battery, alternator and a full service will do the trick" I was happily informed. More dollars came spilling out of a wallet that was already empty and filled with dust and cobwebbs.
For a glorious five days he has been running nicely and I've been all happy thinking the curse has finally been broken.
But... *sigh*... BUT.... it firking hasnt.
Today its back!
The power of Christ did not compel these engine demons to leave :(
So we already agree that using WDSC for IBM i software editing, for free, is pretty cool. But, adding Turnover V100 to it, so you can do everything from one place is even cooler. Once we have added the Turnover perspective to our existing WDSC7 setup then we can flick between perspectives to edit/compile source code, then check in/out of turnover worklists.
1 - Install WDSC
I am going to assume you have already done this. If not then just follow these instructions. Come back here when you're done
Run the latest Turnover Client Install from your V100 ISO Disk (or download it from http://support.softlanding.com). You can install the client software from DOCSCLIENT.iso\Clients\Software - ISO 9660 archive, unpacked size 290,146,213 bytes
To install just execute the T100client.exe:
note: the build number is shown bottom right 13098. At time of writing this is the most recent version of the Turnover V100 client.
It should ask you if you want to upgrade –please select NEW INSTALL
Turnover (from Soft Landings Inc) is a pretty cool Software Change Management system running on ISERIES *cough* IBM i.
NOTICE FOR SOFTLANDING SYSTEMS You are marketing your Change Management Product as 'Turnover for iSeries V100'. But IBM no longer sell the iSeries systems. In fact, IBM haven't sold this machine for a few years now and as we all know - a year in IT is a decade in the real world.
The hardware is the IBM Power System and, as we all know, the operating system is IBM i.
So, isn't it time to rebrand your change management software and call it - Turnover for IBM i V100?
After last weeks engine death – well kind of choking spluttering whimpering suicide - I waited for the AAA recovery truck and had Boris truck to a local garage that foolishly admitted to working on Landrover. All the time thanking the Gods that I signed up for AAA car recovery last year.
Anyway, the garage called me last night confidently saying “Boris is fixed! It was the alternator, which was shorting out and causing the electrical glitches. It finally died, caused a direct short which drained the battery in a minute flat and this caused the breakdown”. Now a more skeptical man than myself may not believe this explanation. I know for a fact that all these engine problems over the last two years are down to the engine being haunted, and not due to any physical problem on this plain of existence. But, as they also told me it has cost me $720 and that includes a new battery, alternator, oil change and mini-service – well who am I to complain?
But I’ve been here before haven’t I?
So, lets review the number of visits to a garage (or *shop* as you yanks say) since that cursed day in September 2011 when I took ownership of Boris the Landrover: