Working system displays:
----------------
LOGON LNXADMIN
z/VM Version 6 Release 3.0, Service Level 1501 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: 0011 RDR, NO PRT, NO PUN
LOGON AT 15:39:03 EST FRIDAY 02/25/22
Command complete
Command complete
HCPCPL040E Device 0600 does not exist
z/VM V6.3.0 2015-08-17 18:51
LNXADMIN AT OSCAR VIA RSCS 2022-02-25 15:39:04 EST FRIDAY
DMSACP723I T (592) R/O
SWPSWA0012I DIAG swap disk defined at virtual address 0300 with
SWPSWA0012I 64988 4K pages of swap space.
SWPSWA0012I DIAG swap disk defined at virtual address 0301 with
SWPSWA0012I 129980 4K pages of swap space.
OSA 0370 ATTACHED TO LNXADMIN 0370
OSA 0371 ATTACHED TO LNXADMIN 0371
OSA 0372 ATTACHED TO LNXADMIN 0372
DO YOU WANT TO IPL LINUX FROM MINIDISK 100? Y/N
y
Booting default (grub2)
----------------------- (followed by a grub menu)
Non-working system displays:
-----------------------
LOGON LNXADMIN
z/VM Version 6 Release 3.0, Service Level 1501 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: 0022 RDR, 0001 PRT, NO PUN
LOGON AT 15:40:27 EST FRIDAY 02/25/22
Command complete
Command complete
HCPCPL040E Device 0600 does not exist
z/VM V6.3.0 2015-08-17 18:51
LNXADMIN AT OSCAR VIA * 2022-02-25 15:40:27 EST FRIDAY
DMSACP723I T (592) R/O
SWPSWA0012I DIAG swap disk defined at virtual address 0300 with
SWPSWA0012I 64988 4K pages of swap space.
SWPSWA0012I DIAG swap disk defined at virtual address 0301 with
SWPSWA0012I 129980 4K pages of swap space.
HCPATR040E Device 0370 does not exist
HCPATR040E Device 0371 does not exist
HCPATR040E Device 0372 does not exist
DO YOU WANT TO IPL LINUX FROM MINIDISK 100? Y/N
----------------------- (nothing else)
Tony Thigpen
Fred Bader wrote on 2/25/22 15:26:
This maybe a dumb question, but is the volume VMFF85 online and attached to
the system? If not, when LNXADMIN logs on, it should get an error message
that the volume is not available and therefore MDISK 0100 won't exist and
can't be IPLed.
It would help if we could see the console messages produced when LNXADMIN
was logged on or XAUTOLOGed. I see OPERATOR is defined as SECUSER, so
those messages should be on the OPERATOR's console as well.
Regards, Fred
_________________________________________________________________________
Fred Bader, IBM Z Washington Systems Center (WSC) - IBM Systems
IBM Corp, 470 Springpark Pl, Suite 950/1000, Herndon, VA 20170-5253
E-mail: fba...@us.ibm.com, Phone: 720-395-5555, Tieline: 676-5555
IBM Z - "The cloud you want with the privacy and security you need"
http://www.ibm.com/systems/z/ - http://www.ibm.com/z15
From: "Tony Thigpen" <t...@vse2pdf.com>
To: LINUX-390@VM.MARIST.EDU
Date: 02/25/2022 03:14 PM
Subject: [EXTERNAL] Re: [PossibleSpam] Re: Suse failed boot after move
to new DS8000
Sent by: "Linux on 390 Port" <LINUX-390@VM.MARIST.EDU>
The profile is simply:
USER LNXADMIN xxxxxxxx 1G 2G BDEG
INCLUDE LNXPDFLT
OPTION LNKNOPAS
MDISK 0100 3390 00001 10016 VMFF85 MR LNX4VM LNX4VM LNX4VM
MDISK 0200 3390 00001 10016 VMFF86 MR LNX4VM LNX4VM LNX4VM
where the profile for lnxpdflt is:
PROFILE LNXPDFLT
***COMMON LINUX DIRMPROFILE**************
COMMAND SET SECUSER OPERATOR
COMMAND SET RUN ON
COMMAND TERM HOLD OFF
COMMAND TERM MORE 001 000
COMMAND SCRE CPO WHI NON
COMMAND SCRE STA GRE REV
COMMAND COUPLE 0600 TO SYSTEM VSW1
CPU 00 BASE
DATEFORMAT ISODATE
IPL CMS PARM FILEPOOL LINUX AUTOCR
MACHINE ESA 8
IUCV ALLOW
OPTION CHPIDV ONE
CONSOLE 0009 3215 T
SPOOL 000C 2540 READER *
SPOOL 000D 2540 PUNCH A
SPOOL 000E 1403 A
LINK MAINT 0190 0190 RR
LINK MAINT 019D 019D RR
LINK MAINT 019E 019E RR
LINK TCPMAINT 0592 0592 RR
I have attached the PROFILE EXEC.
Tony Thigpen
Mark Post wrote on 2/25/22 12:14:
On 2/25/22 07:21, Tony Thigpen wrote:
I am helping a customer move his 6.3 system to a new DS8000. We moved
all the dasd using DDR. After the copy, his LNXADMIN (SUSE) user will
not boot.
He says he logs onto the guest and when it asked 'boot linux?', he
replies 'Y' and nothing seems to happen.
I am not really familiar with zLinux. Is there anything that needs to be
done special to make it moveable by DDR?
As Sam said, it looks like his PROFILE EXEC is doing something that
isn't working. What are the contents? What, if any, messages come out
when he tries to do the IPL manually? Is it an MDISK, or a DEDICATEd
volume?
There shouldn't have been anything special needed to move the volume,
other than keeping the same virtual device number the same (maybe), or
the VOLSER the same, etc. What's the USER DIRECT entry for the guest
look like?
Mark Post
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
(See attached file: profile.exec.txt)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
