The LM is transparent for customer application, i.e. they aren’t affected by the transfer to the target SU. If necessary, it gives the possibility to inform oneself if an LM took place, which happens through the BS2000 commands /SHOW-SYSTEM-INFORMATION and /SHOW-LIVE-MIGRATION-HISTORY.
In the following chapter, the usage of the above commands is described in the context of LM.
Further details can be found in the handbook “BS2000 Commands” [8] with the description of the corresponding commands.
Command /SHOW-SYSTEM-INFORMATION
After a BS2000 has been migrated, the command /SHOW-SYSTEM-INFORMATION issues additional the message NSI6231 or NSI6232 when called with standard parameters, depending on the value of the system parameter MIGHOST:
% NSI6231 LIVE MIGRATION HAS OCCURED; DATA OF THE IPL HOST WILL BE DISPLAYED
or
% NSI6232 LIVE MIGRATION HAS OCCURED; DATA OF THE CURRENTHOST WILL BE DISPLAYED
Example:
/SHOW-SYSTEM-INFORMATION
% NSI6231 LIVE MIGRATION HAS ALREADY TAKEN PLACE; DATA OF IPL HOST WILL BE DISPLAYED
%CONFIGURATION = 390SU- 500-10B
%CURRENT-CONFIGURATION = 390SU- 700-70
%CPU-ID-LIST : ADR 0 = 0602210424000000
% ADR 1 = 0612210424000000
%HSI-ATT : TYPE = IX
% ASF = YES
% OPERATION-MODE = VM2000
%MEMORY-SIZE = 4096 MB
%MINIMAL-MEMORY-SIZE = 4096 MB
%BS2000-ID : NAME = O10BXS
% VERSION = V19.0A0000
% OSD-BC-VERSION = V10.0A0000
% CREATED = 2015-01-19,14:22:52
%IOCONF-ID : NAME = SU500SE1
% VERSION = V19.0A01
% CREATED = 2016-08-16,13:19:25
% FORMAT = IORSF01
%IPL-TIME = 2016-09-26,14:15:40
%SYSTEM-CONF : SYSID = 127
% HOME-PUBSET = SBZ1
% HOST-NAME = BS2PROD
% VM-INDEX = 12
% VM-NAME = VM12PROD
% SYSTEM-NAME = *NONE % SYSPAR-BS2-SEL = *STD
% LIVE-MIG-COUNT = 3
%VM2000-VERSION = V11.5A
%VM2000-MONITOR- OSD-BC-VERSION = V11.0A0000
% SYSTEM: HOST-NAME = ABGSE501
%SYSTEM-TIME- ZONE = +01:00
% PARAMETER: SEASON = S
% SEASON-DIFFERENCE = 01:00
% PREV-CHANGE-DATE = 2016-03-27,02:00:00
% NEXT-CHANGE-DATE = 2016-10-30,03:00:00
% SYNCHRONIZATION = SERVER-CONN-EXT-REF
% EPOCH = 00
The parameter LIVE-MIG-COUNT shows how often this system has been migrated.
From the parameter CONFIGURATION one can see that this VM ha been started initially on a SU500 and the parameter CURRENT-CONFIGURATION shows that it is currently running on a SU700.
The following CPU-ID-LIST shows by default the CPU IDs of the installation on which the system has been loaded (in this example, the CPU ID of the SU500).
The CPU IDs of the installation on which the system is currently running are displayed if the command is called with the parameter SERVER-UNIT=*CURRENT:
/SHOW-SYSTEM-INFORMATION SERVER-UNIT=*CURRENT
%CONFIGURATION = 390SU- 700-70
%CURRENT-CONFIGURATION = 390SU- 700-70
%CPU-ID-LIST : ADR 0 = 6002900126000000
% ADR 1 = 6012900126000000
%HSI-ATT : TYPE = IX
...
The corresponding user-macro is called NSINF and is described in the manual "Executive Macros".
The standard output of the command is influenced by the setup of the system parameter MIGHOST.
System parameter MIGHOST
System data changes because of an LM to a different SU for example the name of the VM2000 monitor system or VM index.
To avoid compatibility problems when an application uses such data (for example as part of a file name), all information functions of the systems deliver also after the LM the data valid at IPL time.
If such compatibility requirements are not given, we recommend to change the system parameter MIGHOST in such a way that current data is output instead of the IPL data.
The parameter can be changed while the system is running.
Further details can be found in the handbook "Introductory Guide to Systems Support" [9] in the description of the system parameter MIGHOST.
Command /SHOW-LIVE-MIGRATION-HISTORY
The command /SHOW-LIVE-MIGRATION-HISTORY delivers additionally also the date and the time of every performed Live Migration.
Example of an output after the first migration of the VM 12 in a SU /390 Cluster:
/SHOW-LIVE-MIGRATION-HISTORY
LM-COUNT DATE TIME CONFIGURATION VM
00000000 2016-12-06 10:07:02 390SU- 500-10B 12
00000001 2016-12-07 09:57:38 390SU- 700-70 12
The system has been loaded on 06.12.2016 at 10:07 on SU500 and migrated to a SU700 on 07.12.2016 at 9:57.