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.
Have you looked at Zend Server 6 which was released in April of this year? Check it out at Zend.com to see the latest in PHP stacks as we now support PHP 5.4. The first thing you notice about Zend Server 6 is the login screen asks you for a user id and password. That is because we now include role based access to the user interface to Zend Server 6. This allows companies that have a strict division between developers and administration to set and enforce these roles appropriately. Enterprise customers can further enhance the experience by tying the admin interface into a LDAP server thus allowing folks to user their normal userid and password to access the interface and a full blown audit trail for changes to configuration files. Otherwise the ADMIN and DEVELOPER user profiles will work fine.
Once logged onto the Zend Server administrative interface, you’ll notice that cleaner and more sleek UI. The folks in R&D spent a lot of time on usability and focused aggressively on a cleaner interface. The initial dashboard shows system statistics as well as events that have recently occurred. And the responsiveness of the screens has tremendously improved over Zend Server 5.
One of the cornerstones to Zend Server 6 is the applications centric environment. This gives the administrators the ability to fine tune the event monitor rules based upon application and not just at the server level. One practical example of this is evidenced by an administrator setting up event notification at the application level thus allowing only the production applications to send event email and leaving the more nebulous applications alone. No need to react of hours cause phpMyAdmin threw a PHP error.
Installation of Zend Server 6 is done in parallel with Zend Server 5. This gives IBM i shops the ability to set up the environment of before going live. Once the environment is ready for production all you need to do is flip around a couple of ports. The default ports administration is placed at 10081 and for web serving is 10080. These values can be changed in the Apache configuration file when ready. This separation from UI and Admin brought the IBM i version of Zend Server in line with other platforms and enhances the security by allowing network administrators to block the port from the public. Zend Server 6.1 is the current version available at Zend .Com and can be downloaded as a complete installable file or as a PTF to Zend server 6.0 which was released back in March of 2013. Full documentation for Zend Server and the tool kits are available and documentation pages and Zend.Com.
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:
OK I have to admit I did not think of this first, I found it when I checked the latest Blog postings on iPlanet! You can find the original here. I just searched on the web to find the IBM … Continue reading →
So this is a technique that I discovered while trying to get WDSSC184.108.40.206 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