Recently I was asked how to execute a command typed in 5250 terminal among multiple sessions. For instance, when you need to create a library DEV on three systems, and you are lazy do copy/paste.
I assume there are many installations which need to go to VIOS 3.1 by October 2020 due to end of support for VIOS 2.x. Because, I did not find any upgrade procedure for “dummies”, I decided to write one which I hope people find useful. I do not cover only the upgrade process itself, but also share some advises how to do it safely and recover in case of troubles. Upgrade Virtual I/O Server to 3.1 is completely different process than before. For instance, you are going to need an extra disk to perform the operation. Interested?
Long story short – how regular VIOS update ended with few weeks investigations completed with the serious VIOS bug and the APAR (IJ25390). The latest VIO releases contain a serious bug which may affect all VIOS/SEA client LPARs on IBM Power Servers.
I don’t think many people noticed this information yet, but recently a project which I was involved for last two years get live. My feeling is that many people do not understand the idea, thus I created a post explaining the functionality and possible usage. Read more about LPARKit below – tool which allows to create LPARs from 5250 and cloning IBM i OS. Continue reading “LPARKit – tool for managing VIOS from 5250 and cloning IBM i OS”
I had a pleasure to attend IBM Technical University conference last week of October in Prague. I also have been given a chance to run four sessions. Read about the conference and other interesting facts below.
As I wrote in the previous post, there might a situation when another/former load source disk become part of the LPAR configuration. IBMi OS configuration allows to run only with one valid load source, therefore the operating system will change a specific sector, making a former load source disk a regular disk. Therefore, this disk can’t be used as the Load Source never again. In this post I will describe what sector need to be changed in order to recover the disk, and reuse it in another configuration.
Process for copying the load source disk is sort of a black box. The copying process is straight forward, but there is no documentation ‘what if’. My assumption is because this is very sensitive operation, IBM does not want us to meddle with the process. I’ve created sort of summary for admins based on my experience ,and research made over hundreds copying processes. I bet you won’t get this information thru any official channel.
I want to introduce IBM iDoctor tool to people who does not know it. Few years ago, I didn’t know the tool either, and I’ve heard lot of wired stories what the aim is. These days, I can’t live without it, and every single serious performance analysis starts with the tool. I want to show you in very simple steps how to do a basic analysis. Not sure if you know, but the tool is available with 45-days free trial. So, you can give a try without paying a single penny, or ordering an expensive consultant. Continue reading “IBM iDoctor for beginners”
Me and many other technicians hate the limitation that the only supported way of migrating the Loadsource disk to a smaller LUN is save/restore IBMi OS. With the method described below, I was able to copy the Loadsource to the smaller disk, and it worked. Continue reading “IBMi – copy the loadsource to a smaller disk”
Have you ever wonder if a LUN delivered from an external storage to your IBMi Lpar is thin provisioned,encrypted or provisioned thru SSD, you can do it from IBMi. Read below about hidden SST macro.