Re: MVS command display

2021-05-25 Thread Jesse 1 Robinson
Thanks Tom. I suspected that my answer was out of date. On each of our systems, 
I have had a unique console id for so long that the 'undefined default' never 
occurs any longer. 

For those who make use of the VTAM console application SMCS, similar issues 
exist. By default, SMCS adopts the operator's userid as a console id. This may 
clash with SDSF. Furthermore, SMCS cannot be run concurrently on multiple 
member of the same sysplex unless a non-default console id is specified. 
Despite this limitation, I like SMCS a lot. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Tom 
Conley
Sent: Tuesday, May 25, 2021 1:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: MVS command display

*** EXTERNAL EMAIL - Use caution when opening links or attachments ***

On 5/25/2021 3:43 PM, Jesse 1 Robinson wrote:
> SDSF uses extended consoles to manage command output. A given console and be 
> active on only one system at a time. If you have a MAS, output from a command 
> issued on one member may well appear on another system. If you have only one 
> member in your SDSDF plex, then never mind. Otherwise:
>
> 1. Logon to one system.
> 2. Get into SDSF.
> 3. Issue SET CONSOLE ?
> 4. You will see this something like this (sorry for the screwy 
> formatting)
> ++
> |   Set Console Name |
> ||
> | Type a console name or leave blank to use  |
> | your user ID as the console name.  |
> ||
> | Extended console name   your-userid  |
> ||
> ||
> | F1=Help  F12=Cancel|
> ++
>
> Repeat this procedure on all sharing systems. The default name is your userid 
> id. On multiple systems, the id may be identical on all sharing systems. If 
> the ids are identical, a command issued on one system will display on 
> whichever system initialized first. You can set the console id on each system 
> to (more or less) anything you want. As long as the id is unique, a  command 
> will be responded to on the system where it's issued.
>

FYI,

SDSF fixed this situation a long time ago.  It is supposed to detect that a 
console id in a sysplex is already in use, and create a unique console id for 
the sysplex.  If it can't create a unique console id, you're supposed to get an 
error message.  If this is really your problem, you should open a case to have 
Rocket fix this.

Regards,
Tom Conley


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: MVS command display

2021-05-25 Thread Tom Conley

On 5/25/2021 3:43 PM, Jesse 1 Robinson wrote:

SDSF uses extended consoles to manage command output. A given console and be 
active on only one system at a time. If you have a MAS, output from a command 
issued on one member may well appear on another system. If you have only one 
member in your SDSDF plex, then never mind. Otherwise:

1. Logon to one system.
2. Get into SDSF.
3. Issue SET CONSOLE ?
4. You will see this something like this (sorry for the screwy formatting)
++
|   Set Console Name |
||
| Type a console name or leave blank to use  |
| your user ID as the console name.  |
||
| Extended console name   your-userid  |
||
||
| F1=Help  F12=Cancel|
++

Repeat this procedure on all sharing systems. The default name is your userid 
id. On multiple systems, the id may be identical on all sharing systems. If the 
ids are identical, a command issued on one system will display on whichever 
system initialized first. You can set the console id on each system to (more or 
less) anything you want. As long as the id is unique, a  command will be 
responded to on the system where it's issued.



FYI,

SDSF fixed this situation a long time ago.  It is supposed to detect 
that a console id in a sysplex is already in use, and create a unique 
console id for the sysplex.  If it can't create a unique console id, 
you're supposed to get an error message.  If this is really your 
problem, you should open a case to have Rocket fix this.


Regards,
Tom Conley

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: MVS command display

2021-05-25 Thread Jesse 1 Robinson
SDSF uses extended consoles to manage command output. A given console and be 
active on only one system at a time. If you have a MAS, output from a command 
issued on one member may well appear on another system. If you have only one 
member in your SDSDF plex, then never mind. Otherwise:

1. Logon to one system. 
2. Get into SDSF.
3. Issue SET CONSOLE ?
4. You will see this something like this (sorry for the screwy formatting)
++
|   Set Console Name |
||
| Type a console name or leave blank to use  |
| your user ID as the console name.  |
||
| Extended console name   your-userid  |
||
||
| F1=Help  F12=Cancel|
++

Repeat this procedure on all sharing systems. The default name is your userid 
id. On multiple systems, the id may be identical on all sharing systems. If the 
ids are identical, a command issued on one system will display on whichever 
system initialized first. You can set the console id on each system to (more or 
less) anything you want. As long as the id is unique, a  command will be 
responded to on the system where it's issued. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lizette Koehler
Sent: Tuesday, May 25, 2021 12:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: MVS command display

*** EXTERNAL EMAIL - Use caution when opening links or attachments ***

Do you have an automation tool that might be changing the command behavor?

We use OPS/MVS to Make White/RED highlighted Non Scrollable as needed


Lizette


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jake Anderson
Sent: Tuesday, May 25, 2021 10:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: MVS command display

Hello

Usually when we issue a MVS display command from SDSF we get immediately get to 
see the output in bold white message and after that we can see either in SYSLOG 
or ULOG. One of our user from operation is issuing the command but doesn't get 
a immediate output in bold white instead it just says 'command issued' and the 
output is seen only in log

Is there any specific user profile definition that I can look to fix this ?

Any pointers or direction are much appreciated.

Jake

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: MVS command display

2021-05-25 Thread Lizette Koehler
Do you have an automation tool that might be changing the command behavor?

We use OPS/MVS to Make White/RED highlighted Non Scrollable as needed


Lizette


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jake Anderson
Sent: Tuesday, May 25, 2021 10:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: MVS command display

Hello

Usually when we issue a MVS display command from SDSF we get immediately get to 
see the output in bold white message and after that we can see either in SYSLOG 
or ULOG. One of our user from operation is issuing the command but doesn't get 
a immediate output in bold white instead it just says 'command issued' and the 
output is seen only in log

Is there any specific user profile definition that I can look to fix this ?

Any pointers or direction are much appreciated.

Jake

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: MVS command display

2021-05-25 Thread Carmen Vitullo
I've never seen the response in white or bold but there is a timeout 
value for command response in SDSF


options then #4 console and response

Carmen
On 5/25/2021 12:33 PM, Jake Anderson wrote:

Hello

Usually when we issue a MVS display command from SDSF we get immediately
get to see the output in bold white message and after that we can see
either in SYSLOG or ULOG. One of our user from operation is issuing the
command but doesn't get a immediate output in bold white instead it just
says 'command issued' and the output is seen only in log

Is there any specific user profile definition that I can look to fix this ?

Any pointers or direction are much appreciated.

Jake

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
*Carmen Vitullo*

/“I am not bound to win, but I am bound to be true. I am not bound to 
succeed, but I am bound to live up to what light I have.” ― Abraham Lincoln/



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


MVS command display

2021-05-25 Thread Jake Anderson
Hello

Usually when we issue a MVS display command from SDSF we get immediately
get to see the output in bold white message and after that we can see
either in SYSLOG or ULOG. One of our user from operation is issuing the
command but doesn't get a immediate output in bold white instead it just
says 'command issued' and the output is seen only in log

Is there any specific user profile definition that I can look to fix this ?

Any pointers or direction are much appreciated.

Jake

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


DSCMON

2021-05-25 Thread Steve Beaver
Does anyone use DSCMON on their systems?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS Technologies

2021-05-25 Thread Seymour J Metz
Yes, COND is ugly, unnatural and a booby trap for the unwary, but I never broke 
myself of the habit of using it. I would, however, want to train a newbie to 
understand it but to use IF/ELSE for new JCL.

Whether I string things together in JCL or in a REXX script depends very much 
on what I am trying to do, and the question of AND/OR logic on completion codes 
is pretty far down my list of considerations.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Steve Smith [sasd...@gmail.com]
Sent: Monday, May 24, 2021 6:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS 
Technologies

The problem I have with COND= is that it's back-asswards.  First, it
specifies conditions to NOT run the step.  You have to keep in mind that
with multiple conditions, any TRUE condition means don't run the step.
Except for ONLY & EVEN, which specify conditions for which the step *will*
run.  Second, the natural way to code a test is to say "if variable
[comparison] value", not the reverse that COND requires.

It's certainly possible to train yourself to grok that, but it's about as
unintuitive as it can be.  The IF / ELSE constructs are a great improvement
in understandability.  You can continue using the old way if you like, and
I don't see any argument that the new way causes any problems.  So what's
the complaint?

For the record, I use both COND and IF as I see fit, but if an OR or AND
rears its head, I'm likely to recast the whole thing into REXX.

sas

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN