Please, let's not start this type of thing with clist. Yes, I know it can
cause confusion.
--
John McKown
Maranatha! <><
Sent from my Vibrant Android phone.
On Jun 13, 2011 12:34 PM, "Ted MacNEIL" wrote:
>REXX clists
There is no such thing.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNE
ADY prompt.
Scott J Ford
From: "Barkow, Eileen"
To: IBM-MAIN@bama.ua.edu
Sent: Mon, June 13, 2011 9:50:53 AM
Subject: TSO STATUS and IKJ56192I/IKJ56211I msgs
we are running Z/OS 1.11.
When i issue the TSO STATUS command in TSO
on some of our lpars, the
In
,
on 06/13/2011
at 08:27 AM, Skip Robinson said:
>Here's a simple solution: make sure that the command response matches
>your Rexx. If your code expects a msgid, then precede STATUS with
>PROFILE MSGID. Otherwise use PROFILE NOMSGID. This guarantees that
>you'll always get the format yo
In
<2144213715-1307989295-cardhu_decombobulator_blackberry.rim.net-1463391740-@b12.c1.bise6.blackberry>,
on 06/13/2011
at 06:21 PM, Ted MacNEIL said:
>At the risk of being pedantic, I disagree.
You are a hypocrite. Apparently it is okay for you to be pedantic but
bad for others to (allegedly)
mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
John McKown
Sent: Monday, June 13, 2011 1:00 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSO STATUS and IKJ56192I/IKJ56211I msgs
But rather common. I sometime say REXX program and other times use
script. The latter especially in a UNIX environment.
On Mon,
>So I assume that when written in REXX whatever it is can also be called a
>clist.
At the risk of being pedantic, I disagree.
They are both scripting languages, but do things in different manners.
So EXECs (REXX) and CLISTs (Command LISTs) are different entities.
-
Ted MacNEIL
eamacn...@yahoo.c
But rather common. I sometime say REXX program and other times use
script. The latter especially in a UNIX environment.
On Mon, 2011-06-13 at 17:34 +, Ted MacNEIL wrote:
> >REXX clists
>
> There is no such thing.
> -
> Ted MacNEIL
> eamacn...@yahoo.ca
> Twitter: @TedMacNEIL
>
> -
X whatever it is can also be called a
clist.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Ted MacNEIL
Sent: Monday, June 13, 2011 1:34 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSO STATUS and IKJ56192I/IKJ56211I msgs
>REXX clists
>REXX clists
There is no such thing.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
rdee
CA technologies
Sr Sustaining Engineer
Tel: +1-952-838-1039
charles.har...@ca.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Barkow, Eileen
Sent: Monday, June 13, 2011 10:13 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSO
astructure Technology Services
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: "Barkow, Eileen"
To: IBM-MAIN@bama.ua.edu
Date: 06/13/2011 08:13 AM
Subject: Re: TSO STATUS and IKJ56192I/IK
ist [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Tom Marchant
Sent: Monday, June 13, 2011 10:24 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSO STATUS and IKJ56192I/IKJ56211I msgs
On Mon, 13 Jun 2011 09:50:53 -0400, Barkow, Eileen wrote:
>i use STATUS in come clists and have to trap the response with REXX
IBM-MAIN@bama.ua.edu] On Behalf Of
Tom Marchant
Sent: Monday, June 13, 2011 10:24 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSO STATUS and IKJ56192I/IKJ56211I msgs
On Mon, 13 Jun 2011 09:50:53 -0400, Barkow, Eileen wrote:
>i use STATUS in come clists and have to trap the response with REXX OUT
: Re: TSO STATUS and IKJ56192I/IKJ56211I msgs
On Mon, 13 Jun 2011 09:50:53 -0400, Barkow, Eileen wrote:
>i use STATUS in come clists and have to trap the response with REXX OUTTRAP and
>the extra field or lack of it throws the clists off (unless I modify them
for each lpar to
>account fo
On Mon, 13 Jun 2011 09:50:53 -0400, Barkow, Eileen wrote:
>i use STATUS in come clists and have to trap the response with REXX OUTTRAP and
>the extra field or lack of it throws the clists off (unless I modify them
for each lpar to
>account for the IKJ* msgs).
IMO, you should code your clists to l
This is controlled by the TSO PROFILE MSGID option.
Looks like your first example is run on a system with MSGID, the second
on a system with NOMSGID.
To change, use TSO PROFILE MSGID to turn on, or TSO PROFILE NOMSGID to
turn it off.
Tom Chicklon
i use STATUS in come cl
Thanks for the PROFILE MSGID info, Binyamin.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Binyamin Dissen
Sent: Monday, June 13, 2011 9:54 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSO STATUS and IKJ56192I/IKJ56211I msgs
On Mon, 13 Jun
Eileen
Check what you have set up in your TSO PROFILE
Issue TSO PROF from any command line. I am guessing that you will see
NOMSGID on the lpars where you do not get the message id.
To switch it back on , issue TSO PROF MSGID
HTH
Mike
On Mon, Jun 13, 2011 at 4:50 PM, Barkow, Eileen wrote:
> we
On Mon, 13 Jun 2011 09:50:53 -0400 "Barkow, Eileen"
wrote:
:>we are running Z/OS 1.11.
:>When i issue the TSO STATUS command in TSO
:>on some of our lpars, the response is preceded by either the IKJ56192I
:>or IKJ56211I msgs. On other lpars, it is not.
:>Does anyone know what causes this?
:>i us
we are running Z/OS 1.11.
When i issue the TSO STATUS command in TSO
on some of our lpars, the response is preceded by either the IKJ56192I
or IKJ56211I msgs. On other lpars, it is not.
Does anyone know what causes this?
i use STATUS in come clists and have to trap the response with REXX OUTTRAP a
20 matches
Mail list logo
