s, I knew that you were a putz.
From: IBM Mainframe Discussion List on behalf of Jon
Perryman
Sent: Monday, July 31, 2023 6:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 30, 2023 at 03:39:46 PM PDT, Seymour J Met
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 30, 2023 at 03:39:46 PM PDT, Seymour J Metz
> wrote:
> I'm saying that you are lying about what we disagree about.
You said I lied again in that Email. Your non-answer is not an answer. What
spe
y
claim to respect.
From: IBM Mainframe Discussion List on behalf of Jon
Perryman
Sent: Sunday, July 30, 2023 6:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 30, 2023 at 01:11:05 PM PDT, Seymour J
:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 30, 2023 at 01:11:05 PM PDT, Seymour J Metz
> wrote:
> You are repeating the same old lie.
What lie are you saying I'm repeating? z/VM console 3215 for screen scraping?
Are you saying you asked a
bject: Re: Ignorant z/OS question
> On Sunday, July 30, 2023 at 09:04:58 AM PDT, Seymour J Metz
> wrote:
> WTF? It has nothing to do with screen scraping. It has to do with addresses
> and device types matching.
Once again Seymour fails to ask even one basic question to determine i
Perryman [jperr...@pacbell.net]
Sent: Sunday, July 30, 2023 4:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 30, 2023 at 09:04:58 AM PDT, Seymour J Metz
> wrote:
> WTF? It has nothing to do with screen scraping. It has to do with addresses
>
> On Sunday, July 30, 2023 at 09:04:58 AM PDT, Seymour J Metz
> wrote:
> WTF? It has nothing to do with screen scraping. It has to do with addresses
> and device types matching.
Once again Seymour fails to ask even one basic question to determine if there
is any merit. Seymour's
Sunday, July 30, 2023 11:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 30, 2023 at 02:05:59 AM PDT, Seymour J Metz
> wrote:
> I was spot on when I wrote that the CP and z/OS definitions had to be in
> synch.
In what world were you spot o
ur J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon
Perryman [jperr...@pacbell.net]
Sent: Sunday, July 30, 2023 12:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Saturday, July 29, 2023 at
>
>
> From: IBM Mainframe Discussion List on behalf
> of Jay Maynard
> Sent: Saturday, July 29, 2023 6:47 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Ignorant z/OS question
>
> Now folks...let's not descend into personal name-ca
repeated personal attacks. Take a look at the history of
> this thread and you will see that I have been restrained by comparison.
>
>
> From: IBM Mainframe Discussion List on behalf
> of Jay Maynard
> Sent: Saturday, July 29, 2023 6:47 PM
&
half of Jon
Perryman [jperr...@pacbell.net]
Sent: Sunday, July 30, 2023 12:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Saturday, July 29, 2023 at 04:33:30 PM PDT, Seymour J Metz
> wrote:
> I'm perfectly willing to be civil with people who are civil,
U
Subject: Re: Ignorant z/OS question
> On Saturday, July 29, 2023 at 09:58:00 PM PDT, Tom Brennan
> wrote:
> Ok, I guess that could mean that if/until someone earns your respect,
> you make fun of them like you did with me, ignore their answers like you
> did with me, and ignore
Sounds good, thanks!
On 7/29/2023 11:29 PM, Jon Perryman wrote:
> On Saturday, July 29, 2023 at 09:58:00 PM PDT, Tom Brennan
wrote:
Ok, I guess that could mean that if/until someone earns your respect,
you make fun of them like you did with me, ignore their answers like you
did with me,
> On Saturday, July 29, 2023 at 09:58:00 PM PDT, Tom Brennan
> wrote:
> Ok, I guess that could mean that if/until someone earns your respect,
> you make fun of them like you did with me, ignore their answers like you
> did with me, and ignore their questions like you did with me.
I give
Ok, I guess that could mean that if/until someone earns your respect,
you make fun of them like you did with me, ignore their answers like you
did with me, and ignore their questions like you did with me.
On 7/29/2023 9:14 PM, Jon Perryman wrote:
I'm civil to those who earn and demonstrate
ion List on behalf of Jay
Maynard
Sent: Saturday, July 29, 2023 6:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Now folks...let's not descend into personal name-calling, how about?
On Sat, Jul 29, 2023 at 4:56 PM Jon Perryman wrote:
> > On Saturday, July 29
e:
> >
> > Wrong again. When running z/OS under VM for production, multiple 3270
> > consoles is the norm.
> >
> >
> > From: IBM Mainframe Discussion List on behalf
> > of Jon Perryman
> > Sent: Saturday, July 29, 2023 5:04 PM
on behalf of Jay
Maynard
Sent: Saturday, July 29, 2023 6:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Now folks...let's not descend into personal name-calling, how about?
On Sat, Jul 29, 2023 at 4:56 PM Jon Perryman wrote:
> > On Saturday, July 29, 2023 at 02
t; Sent: Saturday, July 29, 2023 5:04 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Ignorant z/OS question
>
> > On Saturday, July 29, 2023 at 01:24:04 PM PDT, Phil Smith III <
> li...@akphs.com> wrote:
> > After changing the virtual console address from 03E1 to 0009
__
From: IBM Mainframe Discussion List on behalf of Jon
Perryman
Sent: Saturday, July 29, 2023 5:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Saturday, July 29, 2023 at 01:24:04 PM PDT, Phil Smith III
> wrote:
> After changing the virtual console address from
Wrong again. When running z/OS under VM for production, multiple 3270 consoles
is the norm.
From: IBM Mainframe Discussion List on behalf of Jon
Perryman
Sent: Saturday, July 29, 2023 5:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS
> On Saturday, July 29, 2023 at 01:24:04 PM PDT, Phil Smith III
> wrote:
> After changing the virtual console address from 03E1 to 0009
> linemode output went to SECUSER without artifacts
Congrats Phil. Here is what you need to know:
1. z/OS has many consoles. You don't have any consoles
After changing the virtual console address from 03E1 (matching the CONSOLE
entry in CONSOLxx) to 0009 (matching no z/OS console definition) and reIPLing
the guest, the linemode output went to SECUSER without artifacts, as it did on
our old hosting environment.
I'm convinced based on the
: Thursday, July 27, 2023 8:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Thursday, July 27, 2023 at 03:22:06 AM PDT, Seymour J Metz
> wrote:
> I take it that you can't read. "I would have expected" is not a claim of fact.
Your many expectations are t
Hi Jon,
A SPECIAL (in the directory) can also be DETACHd.
Regards,
David
On 2023-07-27 20:51, Jon Perryman wrote:
> On Thursday, July 27, 2023 at 04:03:52 PM PDT, David Spiegel wrote:
You said: "...Detaching a "console" requires a "DEFINE CONSOLE" ..."
AFAIK, (since VM R6.0) this statement
Jon Perryman wrote:
>Can you explain why this is false or how I have this wrong? Steve said
>device but he really meant to say virtual device. The antonym of
>ATTACH is DETACH but strangely DETACH has many antonyms (e.g. ATTACH,
>DEFINE CONSOLE, DEFINE GRAF, ...). If you detach a console, then the
> On Thursday, July 27, 2023 at 04:03:52 PM PDT, David Spiegel wrote:
> You said: "...Detaching a "console" requires a "DEFINE CONSOLE" ..."
> AFAIK, (since VM R6.0) this statement has never been true.
Hi David,
Can you explain why this is false or how I have this wrong? Steve said device
but
and choose to lie about it?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon
Perryman [jperr...@pacbell.net]
Sent: Thursday, July 27, 2023 12:47 AM
To: IBM-MAIN@LISTSERV.UA.
David is, of course, correct that DETACH doesn't require a DEFINE. I think Jon
meant they were the opposites for the virtual console, rather than
DETACH/ATTACH.
If you want, say, a real tape drive attached to your virtual machine (remember
tape drives?), you (or more likely an operator or
Jon Perryman wrote:
>"detach" is a generic command that eliminates a virtual address
>regardless of how the virtual address was defined. "attach" is for
>attaching real VM addresses to a user at a virtual address. Detaching
>a "console" requires a "DEFINE CONSOLE". Detaching a "GRAF" requires a
Hi Jon,
You said: "...Detaching a "console" requires a "DEFINE CONSOLE" ..."
AFAIK, (since VM R6.0) this statement has never been true.
Regards,
David
On 2023-07-26 23:37, Jon Perryman wrote:
> On Tuesday, July 25, 2023 at 07:14:21 PM PDT, Steve Horein
wrote:
Just out of curiosity, is
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Wednesday, July 26, 2023 5:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Berry van Sleeuwen wrote, in part:
>I guess it doesn't really mat
ERV.UA.EDU] on behalf of Jon
Perryman [jperr...@pacbell.net]
Sent: Thursday, July 27, 2023 12:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Wednesday, July 26, 2023 at 03:49:12 AM PDT, Tony Harminc
> wrote:
>>On Tue, 25 Jul 2023 at 17:25, Seymour J Metz w
> On Wednesday, July 26, 2023 at 03:49:12 AM PDT, Tony Harminc
> wrote:
>>On Tue, 25 Jul 2023 at 17:25, Seymour J Metz wrote:
>> I would have expected 1052-7, 3210 and 3215 support to die at the same time.
> Is there any reason to think that there is/was separate code for these
> three
> On Tuesday, July 25, 2023 at 07:14:21 PM PDT, Steve Horein
> wrote:
> Just out of curiosity, is there such a thing as VM "attach" to reconnect a
> device at a later time?
Phil would need to verify what I'm saying. "detach" is a generic command that
eliminates a virtual address regardless
Berry van Sleeuwen wrote, in part:
>I guess it doesn't really matter what address you use, especially for
>Guest Operating Systems, as long as they are defined in their
>respective configuration members (CONSOLxx for z/OS, SYSTEM CONFIG for
>z/VM, IPL proc for z/VSE).
Right. I'm betting that z/OS
6:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
On Tue, 25 Jul 2023 at 17:25, Seymour J Metz wrote:
>
> I would have expected 1052-7, 3210 and 3215 support to die at the same time.
Is there any reason to think that there is/was separate code for these
three devices
Steve Horein [steve.hor...@gmail.com]
Sent: Tuesday, July 25, 2023 10:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
To my understanding, that sounds correct.
Explicitly removing the NIP *console* definition, though leaving the
address defined/intact in the IODF for lat
On Tue, 25 Jul 2023 at 17:25, Seymour J Metz wrote:
>
> I would have expected 1052-7, 3210 and 3215 support to die at the same time.
Is there any reason to think that there is/was separate code for these
three devices? IIRC their programming specs are identical, or very
close to identical.
k for z/VM.
HTH,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jon
Perryman
Sent: Tuesday, July 25, 2023 2:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, D
ryman
Sent: Tuesday, July 25, 2023 2:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don’t click links or open attachments as it may be a Phishing email,
which can steal your Information and compr
@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don’t click links or open attachments as it may be a Phishing email,
which can steal your Information and compromise your Computer.]
PMFJI here, but when I
David Spiegel wrote:
z/VM has ALWAYS (since VM R6.0.) had the CONSOLE at 009 in the Directory
entry for users by convention.
You could DEF 9 3E1 to change it.
Right, but this guest has one at 3E1. I didn't set it up, nor port it from the
other system; it's possible that whoever did that looked
To my understanding, that sounds correct.
Explicitly removing the NIP *console* definition, though leaving the
address defined/intact in the IODF for later use by MVS console services
(CONSOLxx), would have the same effect as making the device inaccessible,
either through (presumably) bad cabling
> On Tuesday, July 25, 2023 at 04:14:48 PM PDT, Steve Horein
> wrote:
> This is what I was referring to, relating to NIP and IODF:
Phil, you can ignore this topic.
Steve, does it make a difference if the NIP address doesn't exist versus
clearing the NIP address in the IODF? I thought both
On 7/25/2023 2:39 PM, Jon Perryman wrote:
z15 and z16 have hardware consoles (PC's) instead of 3270.
Are you talking about the HMC's and SE's? (whether external or HMA's)
Otherwise the only "PC" I can think of related to a mainframe console is
probably out on an operator's desk, where they
This is what I was referring to, relating to NIP and IODF:
https://www.ibm.com/docs/en/zos/2.4.0?topic=configuration-working-operating-system-consoles
The topic mentions both MVS and VM, so there may be some useful
information.
While I mentioned my request to have "...the NIP *device *be
> On Tuesday, July 25, 2023 at 12:47:52 PM PDT, Tom Brennan
> wrote:
> I don't know what an ICA is in this context, ICA (Integrated Channel
> Adapter) back in the days when we still had channels and 3270 was the
> hardware console. z15 and z16 have hardware consoles (PC's) instead of
I don't know what an ICA is in this context, but your note rang a bell.
When the folks I work with configure a (modern) machine to be used for
TPF, they include this feature code.
8P2980 OSA ICC- 3215 Enablement(this one for a z15)
I've been told this is needed for TPF console
> Phil said: (I'm told) had the virtual console at 0009, but the CONSOLxx has
> it at 03E1.
"virtual console" is not a valid concept for VM CP. "CONSOLE 009 3215" has
nothing to do with a console. Have you ever tried adding both "CONSOLE 009
3215" and "CONSOLE 3E1 3270" to the same user.
> Phil wrote: What does "not supported" mean per se?
The last 3215 connected to IBM computers using an ICA. IBM z computers do not
have an ICA nor byte channel therefore not supported on a z16. I suspect you
can't even define one in the HCD. What was the last IBM computer to have an
ICA.
nt: Monday, July 24, 2023 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Classification: Confidential
Going back to the original post, I seemed to have missed the information about
the operating system release.
z/OS (MVS...) has not supported the 3215 for at least 20
m: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon
Perryman [jperr...@pacbell.net]
Sent: Tuesday, July 25, 2023 2:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 23, 2023 at 09:31:24 PM PDT, Seymour J Metz
> wrote: >
if all three are 3270?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Sunday, July 23, 2023 11:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ign
@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Hi Phil,
z/VM has ALWAYS (since VM R6.0.) had the CONSOLE at 009 in the Directory
entry for users by convention.
You could DEF 9 3E1 to change it.
Regards,
David
On 2023-07-25 12:00, Phil Smith III wrote:
> Jon Perryman wrote:
>&
Hi Phil,
z/VM has ALWAYS (since VM R6.0.) had the CONSOLE at 009 in the Directory
entry for users by convention.
You could DEF 9 3E1 to change it.
Regards,
David
On 2023-07-25 12:00, Phil Smith III wrote:
Jon Perryman wrote:
Steve says there is 1 exception to the hardware console requiring
Jon Perryman wrote:
>Steve says there is 1 exception to the hardware console requiring V
>CN(*),ACT to become the first active console during IPL. He says if
>you disable all z/OS DEV(###) consoles, then the hardware console will
>automatically activate because there is no other console available.
> On Sunday, July 23, 2023 at 08:25:34 PM PDT, Steve Horein
> wrote:
> The only time I have seen NIP messages (those messages prior to VARY
> CN(*),ACTIVATE being accepted) on a native MVS LPAR was when the NIP device
Hi Phil, Sorry for the long delay.but I had other things to do. Steve may
M-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Classification: Confidential
ISTR the some of the older "console" support was removed in the indicated
timeframe. E.g. 1052
I cannot say for certain that the 3215 code was removed at that time.
-Original Message-
From: IBM Main
h III
Sent: Monday, July 24, 2023 12:48 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don’t click links or open attachments as it may be a Phishing email,
which can steal your I
IN@LISTSERV.UA.EDU] on
> behalf of Mike Schwab [mike.a.sch...@gmail.com]
> > Sent: Tuesday, July 25, 2023 12:48 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Ignorant z/OS question
> >
> > https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg34585.htm
STSERV.UA.EDU] on
> behalf of Mike Schwab [mike.a.sch...@gmail.com]
> > Sent: Tuesday, July 25, 2023 12:48 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Ignorant z/OS question
> >
> > https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg34585.htm
On Tue, 25 Jul 2023 at 14:44, Mark Jacobs
<0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
>
> I can't confirm, but I think BTAM/SP never made it past MVS/XA and went out
> of support with MVS/ESA.
>
> Mark Jacobs
Even if the BTAM code still works, it's less than obvious to me what
-
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> Mike Schwab [mike.a.sch...@gmail.com]
> Sent: Tuesday, July 25, 2023 12:48 AM
> To: IBM-M
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Mike Schwab [mike.a.sch...@gmail.com]
Sent: Tuesday, July 25, 2023 12:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg34585.html
On Mon
https://www.mail-archive.com/ibmvm@listserv.uark.edu/msg34585.html
On Mon, Jul 24, 2023, 06:32 Phil Smith III wrote:
> Shmuel wrote:
> >That looks like the result of CP, HCD and MCS not specifying the same
> >device type. What happens if all three are 3215? What happens if all
> >three are
Shmuel asked:
>Do you have the URL for the Tracy Dean paper?
Yes, I've read it.
>Does it spell out all the pieces?
Probably, but as I said before, it makes enough assumptions that I can't
understand what to do.
Alan Staller wrote:
>Going back to the original post, I seemed to have missed the
Do you have the URL for the Tracy Dean paper? Does it spell out all the pieces?
From: IBM Mainframe Discussion List on behalf of
Allan Staller
Sent: Monday, July 24, 2023 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Mainframe Discussion List On Behalf Of
Phil Smith III
Sent: Friday, July 21, 2023 5:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don’t click links or open attachments as it may be a Phishing
List on behalf of
Phil Smith III
Sent: Monday, July 24, 2023 7:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Shmuel wrote:
>That looks like the result of CP, HCD and MCS not specifying the same
>device type. What happens if all three are 3215? What happens if all
Shmuel wrote:
>That looks like the result of CP, HCD and MCS not specifying the same
>device type. What happens if all three are 3215? What happens if all
>three are 3270?
I know what CP is :)
HCD and MCS -- I assume one of these is the CONSOLE stuff in CONSOLxx; which is
that, and where is the
-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Sunday, July 23, 2023 11:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Well, this is interesting. Tried again just now with TERMINAL CONMODE 3215. It
comes up, and I see SECUSER output. The only
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> The Devil is in the details. There are relevant factors on both the CP and
> MVS side.
Phil, you need to be weary of Seymour's responses. His lack of problem solving
skills and his hyper-focus on irrelevant details is leadi
@pacbell.net]
Sent: Sunday, July 23, 2023 10:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Hi Phil, I have some good news and bad news.
> Well, this is interesting. Tried again just now with TERMINAL CONMODE 3215.
> The only weirdness is that much of the o
@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
> On Sunday, July 23, 2023 at 04:28:48 PM PDT, Seymour J Metz
> wrote:
> Your not keeping your MVS and VM in synch; 3E1 should be a 3215 on both or a
> 3270 on both.
Some devices must be in synch (e.g. disk drives). On the other hand, s
The only time I have seen NIP messages (those messages prior to VARY
CN(*),ACTIVATE being accepted) on a native MVS LPAR was when the NIP device
defined in the IODF was not available, I believe due to some cabling
issues. In that situation, all NIP messages were routed to the SE/HMC
System
ould be a 3215 on both or a
3270 on both.
From: IBM Mainframe Discussion List on behalf of
Phil Smith III
Sent: Sunday, July 23, 2023 5:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Norman wrote:
>I'd have to try it. 3215s have
Hi Phil, I have some good news and bad news.
> Well, this is interesting. Tried again just now with TERMINAL CONMODE 3215.
> The only weirdness is that much of the output is oddly formatted.
> B- *10.09.46 *CBR3002E Library LATL00 no longer u
> sable.
n List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Saturday, July 22, 2023 6:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Jon Perryman wrote:
>I need you to stop overthinking z/OS console. It's become very simple
>since IBM rewrot
Your not keeping your MVS and VM in synch; 3E1 should be a 3215 on both or a
3270 on both.
From: IBM Mainframe Discussion List on behalf of
Phil Smith III
Sent: Sunday, July 23, 2023 5:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS
Norman wrote:
>I'd have to try it. 3215s have been gone for decades.
>I used an attached or dialed 3270 for MVS. For the guest,
>you probably have a Cons defined as 009 or 01F, as 3215.
Right, at 3E1, which is also in CONSOL00:
CONSOLE DEVNUM(3E1) ROUTCODE(ALL)
UNIT(3277-2)
Norman wrote:
>You told VM it's a 3215, but did you tell z/OS?
>You may be seeing strange output from incompatible
>output streams. I always have a 3215 defined in HCD.
So if I change the CONSOLE statement from 3277-2 (yeah, yeah, 3270-X, haven't
bothered yet) to 3215 that might fix that?
Well, this is interesting. Tried again just now with TERMINAL CONMODE 3215. It
comes up, and I see SECUSER output. The only weirdness is that much of the
output is oddly formatted (copied from SECUSER's screen, in linemode):
B- *10.09.46 *CBR3002E Library LATL00
.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Saturday, July 22, 2023 6:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS
Jon Perryman wrote:
>I need you to stop overthinking z/OS console. It's become very simple
>since IBM rewrote it several years ago. When running on a 3215 console
>printer, lines are printed and when running on a 3270, it's a
>fullscreen interface (like every other fullscreen application such as
Hi Phil,
I need you to stop overthinking z/OS console. It's become very simple since IBM
rewrote it several years ago. When running on a 3215 console printer, lines are
printed and when running on a 3270, it's a fullscreen interface (like every
other fullscreen application such as xedit).
(Wow, this thread is getting long! Sorry about that)
Jon Perryman is still endeavoring to help me, which is appreciated:
>The DEFINE GRAF did nothing useful. SECUID is associated with the VM
>user's CONSOLE definition. If you look at the z/OS syslog, you will
>find the V CN(*),ACT did not come
Resending with formatting corrected. Sorry but listservs don't play well with
yahoo email.
> CP SEND CP ETPGZ1D DEFINE GRAF FFF
> CP SEND CP ETPGZ1D VINPUT VMSG VARY CN(*),ACT
> I do wonder if this will Just Work at IPL time
The DEFINE GRAF did nothing useful. SECUID is associated with the VM
> CP SEND CP ETPGZ1D DEFINE GRAF FFF
> CP SEND CP ETPGZ1D VINPUT VMSG VARY CN(*),ACT
> I do wonder if this will Just Work at IPL time
The DEFINE GRAF did nothing useful. SECUID is associated with the VM user's
CONSOLE definition. If you look at the z/OS syslog, you will find the V
CN(*),ACT
Alan Altmark wrote:
>And if you haven't done so, please read the white paper Tracy Dean
>referenced in her post. It is focused on this aspect of managing z/OS
>guests. We spent a lot of time figuring out how to make it all come
>together. (And you may remember me asking related questions on
@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Shmuel wrote:
>BTW, if you are running z/OS rather than the free MVS then you
>probably want UNIT(3270-X) for your CONSOLE definitions.
You mean instead of UNIT(3277-2)? What does this do for me? I assume it makes
it an adaptabl
Shmuel wrote:
>BTW, if you are running z/OS rather than the free MVS then you
>probably want UNIT(3270-X) for your CONSOLE definitions.
You mean instead of UNIT(3277-2)? What does this do for me? I assume it makes
it an adaptable 327x instead of just a 3277-2?
Subject: Re: Ignorant z/OS question
Shmuel wrote:
>Your virtual machine definition has to be in synch with the guest OS.
>Your console definitions are part of that.
Right, I meant to add that of course I added that SPECIAL to the guest's
directory entr
Shmuel wrote:
>Your virtual machine definition has to be in synch with the guest OS.
>Your console definitions are part of that.
Right, I meant to add that of course I added that SPECIAL to the guest's
directory entry, too.
--
: Re: Ignorant z/OS question
Well, doh: I finally decided to just try it:
CP SEND CP ETPGZ1D DEFINE GRAF FFF
CP SEND CP ETPGZ1D VINPUT VMSG VARY CN(*),ACT
...and now I'm seeing output as SECUSER!
I do wonder if this will Just Work at IPL time, or not until that VARY is
issued. I guess I'll find out
Well, doh: I finally decided to just try it:
CP SEND CP ETPGZ1D DEFINE GRAF FFF
CP SEND CP ETPGZ1D VINPUT VMSG VARY CN(*),ACT
...and now I'm seeing output as SECUSER!
I do wonder if this will Just Work at IPL time, or not until that VARY is
issued. I guess I'll find out when I get a chance.
So
Jon Perryman wrote:
>If I remember correctly, a 3215 is 132 character print which is why
>messages are wrapping. I'm guessing that 3270 mode does not print some
>message attributes but in 3215 mode enables them because of the free
>space. Issue a console command to remove these if you don't
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Thursday, July 20, 2023 2:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Shmuel wrote:
>Define a 3270 address that you can D
: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Phil Smith III [li...@akphs.com]
Sent: Thursday, July 20, 2023 11:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ignorant z/OS question
Jon Perryman kindly offered more thoughts. I've been doing VM for over forty
years, though
1 - 100 of 115 matches
Mail list logo
