Planet i

For me, just maybe.  I'm going to at least give this a solid look.

We have a loose migration plan for all of our x64-based Microsoft Windows servers to IBM Power Systems.  All except our Active Directory servers.  We use those for Group Policy, Domain authentication, Domino web authentication, DNS and a few other familiar functions.

As per ZDNet, the release of Samba 4 appears to be a viable alternative to Active Directory.  More to come once I dig a bit more information about it.  I wonder if I can run it on IBM i?   :)

http://www.zdnet.com/samba-4-released-brings-free-alternative-to-active-directory-7000008654/

Read the original at Steve Pitcher.

For me, just maybe.  I'm going to at least give this a solid look.

We have a loose migration plan for all of our x64-based Microsoft Windows servers to IBM Power Systems.  All except our Active Directory servers.  We use those for Group Policy, Domain authentication, Domino web authentication, DNS and a few other familiar functions.

As per ZDNet, the release of Samba 4 appears to be a viable alternative to Active Directory.  More to come once I dig a bit more information about it.  I wonder if I can run it on IBM i?   :)

http://www.zdnet.com/samba-4-released-brings-free-alternative-to-active-directory-7000008654/

Read the original at Steve Pitcher.

The open source PHP Toolkit enables PHP applications to call procedures (functions) that are defined within RPG service programs on IBM i. (For more information on the toolkit, see my toolkit information page.)

Here’s an example that will work with PHP Toolkit API version 1.4.0 or higher. I also included some ‘boilerplate’ to show best practices for connecting to the toolkit and checking for a successful connection. The illustration of how to call a procedure is in the second half.

<?php
require_once('ToolkitService.php');

// connect to toolkit using DB2 credentials (can also leave blank for default authority)
try {
    $conn = ToolkitService::getInstance('*LOCAL', 'MYUSER', 'MYPASS');
} catch (Exception $e) {
    // Determine reason for failure.
    // Probably database authentication error or invalid or unreachable database.
    $code = $e->getCode();
    $msg = $e->getMessage();

    switch ($code) {
        case 8001:
            // "Authorization failure on distributed database connection attempt"
            // Usually means a wrong DB2 user or password
            echo 'Could not connect due to wrong user or password.';
            break;
        case 42705:
            echo 'Database not found. Try WRKRDBDIRE to check.';
            break; 
        default:
            echo 'Could not connect. Error: ' . $code . ' ' . $msg;
            break;
    } //(switch)
    die; // couldn't connect...handle this however you wish     
} //(try/catch)

// set stateless mode for easy testing (no 'InternalKey' needed).
// (setOptions() introduced in v1.4.0)
$conn->setOptions(array('stateless'=>true));

/* If you wish to test this script but you don't have a real service program,
 * use parseOnly and parseDebugLevel as shown below.
 * No program will be called and you'll get your original values back.
 * Simply uncomment the next line to try this great testing feature of the toolkit.
*/
//$conn->setOptions(array('parseOnly'=>true, 'parseDebugLevel'=>1));

// define several input/output params
$params[] = $conn->AddParameterChar('in', 1,'Division', 'DIV', 'A');
$params[] = $conn->AddParameterChar('in', 6,'Product', 'PROD', '123456');
$params[] = $conn->AddParameterPackDec('both', 7, 2, 'Quantity', 'QTY', '4.53');
$params[] = $conn->AddParameterZoned('out', 5, 2, 'Price', 'PRICE', '0');

// define a procedure return param. Can be any type, even a data structure
$retParam[] = $conn->AddParameterInt32('out', '4-byte int', 'MYINT', '13579');

/* Call service program procedure. 
 * In this example, assume your program is MYLIB/MYPGM and has a procedure/function 'myproc'
 * (procedure name is case-sensitive).
 * Note: specify optional procedure name in parameter 5, an array with associative index 'func'.
*/
$result = $conn->PgmCall('MYPGM', 'MYLIB', $params, $retParam, array('func'=>'myproc'));

if (!$result) {
    echo 'Error calling program. Code: ' . $conn->getErrorCode() . ' Msg: ' . $conn->getErrorMsg();
}

echo 'Called program successfully.<BR><BR>';
echo 'Input/output params: QTY: ' . $result['io_param']['QTY'] . ' PRICE: ' . $result['io_param']['PRICE'] . '<BR>'; 
echo 'Procedure return param MYRESULT: ' . $result['retvals']['MYRESULT']; 

/* 
The above will output something like:

Called program successfully.

Input/output params: QTY: 4.53 PRICE: 0.00
Procedure return param MYRESULT: 13579

*/

Read the original at Alan Seiden Consulting: PHP and IBM i Expertise.

 

No question, No contest...

I am just returning from two weeks in Asia (Taipei and Shenzhen specifically). While there, I had the opportunity to engage and interact with a number of medium and large companies who are using IBM Power Systems, IBM i and DB2 for i to run their core business.

Needless to say, our beloved system is alive and well in so many major institutions around the world. As a side note, it would be really interesting (and thoroughly impossible) to know just how much electronic money flows on daily basis through the so called "legacy" systems designated by the simple letters of "i" and "z". Mind boggling I'm sure.

While interacting with my clients, I came to the realization that very few of them are using IBM i 7.1. For some strange reason they are planning to move, or have recently moved to 6.1. When I dug a bit deeper, I found that the general conscience was that 6.1 is "stable", and that 7.1 might not be. The rationale being that 7.1 is the most recent, thus "newest" code base. It needs time to be broken in. Frankly, this is old and outdated thinking.

After much head scratching on my part, I politely told my clients (and their anxious IBM counterparts) "you are mistaken, AND you are missing the boat".

The notion that IBM i version 7 release 1 is somehow not stable, not ready for action, not worthwhile, is simply ridiculous.

The code base has been available and in production for well over two years! The effort and energy to upgrade to 7.1 is the same as 6.1, yet the return on that investment (i.e. moving to 7.1) is way higher in my opinion - especially when it comes to DB2 for i and data centric programming. Add to this the steady cadence of IBM i 7.1 technology refreshes and you have a clear choice, either:

a) keep really current with the latest features, functions and benefits

  -or-

b) continue to fall further and further behind in capabilities and your ability to meet requirements

Furthermore, if you find yourself in a position to explain and/or defend DB2 for i against competitive technology, you better be talking about what's current, not what is 5, or even 7 years old.

The Bottom Line

If you are not already running IBM i 7.1 (and DB2 within), you should have plans on the drawing board to upgrade sooner than later.

If your plans have version 6 release 1 has the final destination, get the eraser (aka "rubber" for the British readers), remove the number "6" and write in the number "7", and be sure to add a line:  "plus TR5".

Keep all your implementation, testing and roll out plans in place, as this is still best practice.

Read and understand the 6.1 and 7.1 memo to users BEFORE testing and BEFORE going live.

Of course, if you need any kind of assistance, or rationale for the upgrade, certainly reach out. If you have some solution or application that for some reason isn't capable of running on 7.1, let us know that too.

Read the original at DB2 for i.

 

No question, No contest...

I am just returning from two weeks in Asia (Taipei and Shenzhen specifically). While there, I had the opportunity to engage and interact with a number of medium and large companies who are using IBM Power Systems, IBM i and DB2 for i to run their core business.

Needless to say, our beloved system is alive and well in so many major institutions around the world. As a side note, it would be really interesting (and thoroughly impossible) to know just how much electronic money flows on daily basis through the so called "legacy" systems designated by the simple letters of "i" and "z". Mind boggling I'm sure.

While interacting with my clients, I came to the realization that very few of them are using IBM i 7.1. For some strange reason they are planning to move, or have recently moved to 6.1. When I dug a bit deeper, I found that the general conscience was that 6.1 is "stable", and that 7.1 might not be. The rationale being that 7.1 is the most recent, thus "newest" code base. It needs time to be broken in. Frankly, this is old and outdated thinking.

After much head scratching on my part, I politely told my clients (and their anxious IBM counterparts) "you are mistaken, AND you are missing the boat".

The notion that IBM i version 7 release 1 is somehow not stable, not ready for action, not worthwhile, is simply ridiculous.

The code base has been available and in production for well over two years! The effort and energy to upgrade to 7.1 is the same as 6.1, yet the return on that investment (i.e. moving to 7.1) is way higher in my opinion - especially when it comes to DB2 for i and data centric programming. Add to this the steady cadence of IBM i 7.1 technology refreshes and you have a clear choice, either:

a) keep really current with the latest features, functions and benefits

  -or-

b) continue to fall further and further behind in capabilities and your ability to meet requirements

Furthermore, if you find yourself in a position to explain and/or defend DB2 for i against competitive technology, you better be talking about what's current, not what is 5, or even 7 years old.

The Bottom Line

If you are not already running IBM i 7.1 (and DB2 within), you should have plans on the drawing board to upgrade sooner than later.

If your plans have version 6 release 1 has the final destination, get the eraser (aka "rubber" for the British readers), remove the number "6" and write in the number "7", and be sure to add a line:  "plus TR5".

Keep all your implementation, testing and roll out plans in place, as this is still best practice.

Read and understand the 6.1 and 7.1 memo to users BEFORE testing and BEFORE going live.

Of course, if you need any kind of assistance, or rationale for the upgrade, certainly reach out. If you have some solution or application that for some reason isn't capable of running on 7.1, let us know that too.

Read the original at DB2 for i.

I need your feedback!

What do you think are some of the most beneficial websites, news publications, social media outlets, or groups that has helped you in your IBM i career and why? For example, do you get great advice when you post on a certain LinkedIn group? Or has twitter helped you stay informed on what is happening in the market?

Leave your comments below and help us understand what has influenced you the most.

Keep in touch.

Read the original at GSLMUG.

After attending and speaking at COMMON Sweden in Stockholm, Data3 approached me to answer some questions for the latest user group magazine. Their magazine is published and available here. While much of the magazine is in Swedish, some, including my Q&A, is in English.

Here is the ‘interview’..

What Would Trevor Do?

Question:
Hello Trevor,
Thank you for attending and contributing to our conference in
October. Among many things you are right now the lead of the
hashtag #ibmistepup on twitter. Could you please explain what
this is all about, and why it’s important from your point of view?

Answer:
As you know, I am an advocate for improving the perception of the platform. IBM i is a modern, integrated, scalable, robust business platform running on the best hardware from IBM. Given the rich heritage of the platform and the longevity of the people and the applications, there are many people in the community who still regard the platform as the same as it was 30 years ago. For many of these people, the platform has defined their career, and as they get older, change is difficult as they are required to move out of their (very comfortable) comfort zone of AS/400 or iSeries.

When I attended IBM Power Systems Technical University, I talked to many people about the platform. I presented a session called “Promoting IBM i and its future to your Business”, and that sparked many conversations also. I discovered three very distinct groups of attendees, and while I did not talk with everyone, this seemed to be a trend. One group was scared and complaining bitterly about the platform not being the same as they knew it. Why they were even attending a Power Systems conference was a question I never asked. The second group were confused, wondering what to do with their platform, wondering how to move forward, wondering how to convince their business that the platform was the best business platform and worthy of investment, etc. The third group were positive about the future of the platform, the future of the platform in their business, and were extremely passionate and positive about their own future.

I have concluded that each group can be described with one word – in order: Conflicted, Confused, Confident. The most intriguing part for me was that everyone in those groups used a particular name for the platform. Conflicted people called it AS/400. Confused people called it iSeries. Confident people called it IBM i. What a revelation! I donít believe that by just using a particular brand name was the cause of these three conditions, but I thought that it might be the first place to start. If the community saw the platform as modern, integrated, scalable, robust, they would call it IBM i.

So I endeavored to use this thought to convince the community that we need to come together on our perception of the platform, and the brand is a good place to start. What came to mind was for the community to step up. I decided to start the Twitter campaign to ask the community to step up. I will tweet ideas and thoughts, and point out where websites and promotions are not geared towards IBM i. I will eventually build some support for this effort into one of my websites, and will provide material to help those who wish to become engaged. This effort is simply one more piece of noise to add to the community promoting IBM i and its future.

Please join in!

Now you:
Wanna play? Twitter needs your #IBMiStepUp hashtag!

Read the original at Angus' Blog.

A couple of new features have been added to the HA4i product as a result of customer requests. Auditing is one area where HA4i has always been well supported but as customers get used to the product they find areas … Continue reading →

Read the original at Simply i.

Here's a piece I wrote for MC Press Online.  Check it out.

In the Wheelhouse: Selling the Metal

Let's dissect two studies that put IBM i at the top of the list for lowest total cost of ownership, total cost of acquisition, and total amounts of awesome! You want justification? You got it.

ITG Studies to Help You Sell the Metal

International Technology Group (ITG) recently published two studies that talk about total cost of ownership, total cost of acquisition, risk exposure, cost of downtime, and security/malware considerations for the IBM i. The contents, in general, are things we know already: IBM i on Power Systems is the best platform to run our businesses on because of the cost reductions, consolidation, integration, security, simplicity, and the operating environment's virus resistance. Although some of this is old news, there are some great facts in here, so we need to dissect it a little bit. Why? Have you ever had to justify IBM i to a decision-maker? Wouldn't you love to have some key published information at your disposal? Absolutely. Those platform features I mentioned are a tall order to fill on most systems and may even sound like a bunch of hot air to those outside the IBM i community. Think about it. If you were a Windows administrator and lived only in the Windows world, what would you think if I told you that I could sell you a widely deployed operating system that had no known viruses? You probably wouldn't believe me.

Read the full article here.

Read the original at Steve Pitcher.

Here's a piece I wrote for MC Press Online.  Check it out.

In the Wheelhouse: Selling the Metal

Let's dissect two studies that put IBM i at the top of the list for lowest total cost of ownership, total cost of acquisition, and total amounts of awesome! You want justification? You got it.

ITG Studies to Help You Sell the Metal

International Technology Group (ITG) recently published two studies that talk about total cost of ownership, total cost of acquisition, risk exposure, cost of downtime, and security/malware considerations for the IBM i. The contents, in general, are things we know already: IBM i on Power Systems is the best platform to run our businesses on because of the cost reductions, consolidation, integration, security, simplicity, and the operating environment's virus resistance. Although some of this is old news, there are some great facts in here, so we need to dissect it a little bit. Why? Have you ever had to justify IBM i to a decision-maker? Wouldn't you love to have some key published information at your disposal? Absolutely. Those platform features I mentioned are a tall order to fill on most systems and may even sound like a bunch of hot air to those outside the IBM i community. Think about it. If you were a Windows administrator and lived only in the Windows world, what would you think if I told you that I could sell you a widely deployed operating system that had no known viruses? You probably wouldn't believe me.

Read the full article here.

Read the original at Steve Pitcher.