Re: SLES12 Bug?

2016-05-02 Thread Mark Post
>>> On 5/2/2016 at 03:58 PM, Frank Wolfe wrote: > These values are exactly the same as what you posted. > > I have used this media before for a previous install. > > The dasd I am attempting to use was also used before with the same media. > > As Mike M. suggested, all

Re: SLES12 Bug?

2016-05-02 Thread Frank Wolfe
These values are exactly the same as what you posted. I have used this media before for a previous install. The dasd I am attempting to use was also used before with the same media. As Mike M. suggested, all was formatted again. Frank On Mon, May 2, 2016 at 3:28 PM, Mark Post

Re: SLES12 Bug?

2016-05-02 Thread Mark Post
>>> On 5/2/2016 at 01:58 PM, Frank Wolfe wrote: > Hi there > > I am in the process of doing an SLES 12 SP1 install using ssh as the option > and I keep getting this error. > > > [image: Inline image 1] > > Is there any reason for this? Please check the media you

Re: SLES12 Bug?

2016-05-02 Thread Michael MacIsaac
Frank, Then it definitely sounds like a bug. -Mike On Mon, May 2, 2016 at 2:51 PM, Frank Wolfe wrote: > Mike > > No luck. I tried all of the above. > > On Mon, May 2, 2016 at 2:12 PM, Michael MacIsaac > wrote: > > > Frank, > > > > I've seen that

Re: SLES12 Bug?

2016-05-02 Thread Frank Wolfe
Mike No luck. I tried all of the above. On Mon, May 2, 2016 at 2:12 PM, Michael MacIsaac wrote: > Frank, > > I've seen that where the installer finds an old LVM signature on the disk. > Yes, you could argue it's a bug. > > And then as I recall it can be difficult to get

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Will, Chris
Well the #cp disc worked. I will have to check but I think I just issued a DISC after the force of racfvm. Chris Will Systems Software (313) 549-9729 Cell cw...@bcbsm.com -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott Rohling Sent:

Re: SLES12 Bug?

2016-05-02 Thread Michael MacIsaac
Frank, I've seen that where the installer finds an old LVM signature on the disk. Yes, you could argue it's a bug. And then as I recall it can be difficult to get rid of. I recall doing something like IPLing CMS and issuing a CMS FORMAT against it to be sure the signature is wiped out. Then a

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Alan Altmark
On Monday, 05/02/2016 at 05:40 GMT, Scott Rohling wrote: > I should have said after logging on to OPERATOR -- issue SET SYSOPER > OPERATOR before the #CP DISC. It hopefully got set to SYSOPER itself but > this makes sure. > > To explain -- if OPERATOR is logged off -

SLES12 Bug?

2016-05-02 Thread Frank Wolfe
Hi there I am in the process of doing an SLES 12 SP1 install using ssh as the option and I keep getting this error. [image: Inline image 1] Is there any reason for this? Have a good day Frank -- For LINUX-390 subscribe /

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Scott Rohling
Yes it probably would --my automatic reaction to this is to get OPERATOR back as SYSOPER and keeping that operator log going... Thanks for the reminder -- that would be more expedient if you're in a pinch..plus with RACF down - logging into OPERATOR might be difficultSo good

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Rothman, Peter
Would a "TERM MODE VM" work? That is before the "IPL 190" -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott Rohling Sent: Monday, May 02, 2016 1:40 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Instructions for z/VM RSU1601 are not working in

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Scott Rohling
I should have said after logging on to OPERATOR -- issue SET SYSOPER OPERATOR before the #CP DISC. It hopefully got set to SYSOPER itself but this makes sure. To explain -- if OPERATOR is logged off - the next lucky guest with the right level of CP classes (A,B, etc) gets set to SYSOPER and

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Scott Rohling
I suspect you have been made OPERATOR because OPERATOR is logged off. Enter QUERY SYSOPER to see If it is RACMAINT then: - logoff RACMAINT - Logon OPERATOR and then #CP DISC to leave it running - Logon to RACMAINT as you did before Scott Rohling On Mon, May 2, 2016 at 10:22 AM, Will,

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Will, Chris
Here is what I am doing. First force out RACFVM. 13:17:53 FORCE RACFVM RACFVM : CONNECT= 00:06:45 VIRTCPU= 000:00.08 TOTCPU= 000:00.10 RACFVM : LOGOFF AT 13:17:53 EDT MONDAY 05/02/16 BY OPERATOR

Re: Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Scott Rohling
Can you show the lines from the console when you do the 'IPL 190' ? It almost sounds like you are still in CP -- after the IPL 190 (and hitting ENTER when you see VM READ) you should see some messages like this: i 190 z/VM V6.3.02016-03-20 17:29 DMSACP723I D (192) R/O DMSACP723I B (305)

Instructions for z/VM RSU1601 are not working in regards to RACF

2016-05-02 Thread Will, Chris
I got through the service all portion of the upgrade and am now trying to figure out the RACFCONV instructions from VM65719. It says to run the following commands but I keep getting a CP UNKNOWN command after the RACFCONV command (or any other cms command). Is this correct? The RACF database