Re: How to suppress Message in REXX App (SAMPLE)

[McKown, John]

Ouch. Doing that sort of polling makes me cringe. And inspires an idea (perhaps 
insane). Write an APF authorized TSO command which can do an ISGENQ on any 
QNAME / RNAME (even a restricted one) with the WAIT option. When acquired, 
immediately release the ENQ and exit. It might even have a "timeout" option. 
Yes, I know that the interval between the ending of this command and the 
ALLOCATE introduces a "race" condition. But you can then loop back to the 
ISGENQ command if the ALLOCATE fails due to "in use". 

I know, I'm complicating things in order to save CPU. In most shops, this might 
be foolishness. In my shop, it is expected and even necessary to help maintain 
the viability of the z system in an environment which desperately wants to be 
MS-Windows only.

-- 
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com


Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Dana Mitchell
> Sent: Monday, June 04, 2012 7:34 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: How to suppress Message in REXX App (SAMPLE)
> 
> On Sun, 3 Jun 2012 11:47:23 -0500, Paul Gilmartin 
>  wrote:
> >
> >Should I infer from this that conversely it runs concurrently
> >in background and does not tie up the terminal  if output is
> >directed to SYSOUT or ODS?  If so the above EXEC needs a
> >WAIT to guarantee that the output is complete.  (Or does
> >ENQ SHR handle this?)
> >
> >-- gil
> >
> 
> ENQ does not handle this.  I wrote a rexx a long time ago 
> that would issue any HSM command and trap the output as 
> suggested earlier in this thread.  Long running commands 
> would cause the ALLOCATE command to fail due to dataset in 
> use.  I had to add a loop issuing: 
> 
> Address ispexec 'LMINIT DATAID(TRAP) Dataset('dsname') ENQ(SHR)' 
> 
> until it returned RC =0.  Crude, but effective.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> 

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

Re: How to suppress Message in REXX App (SAMPLE)

[Dana Mitchell]

On Sun, 3 Jun 2012 11:47:23 -0500, Paul Gilmartin  wrote:
>
>Should I infer from this that conversely it runs concurrently
>in background and does not tie up the terminal  if output is
>directed to SYSOUT or ODS?  If so the above EXEC needs a
>WAIT to guarantee that the output is complete.  (Or does
>ENQ SHR handle this?)
>
>-- gil
>

ENQ does not handle this.  I wrote a rexx a long time ago that would issue any 
HSM command and trap the output as suggested earlier in this thread.  Long 
running commands would cause the ALLOCATE command to fail due to dataset in 
use.  I had to add a loop issuing: 

Address ispexec 'LMINIT DATAID(TRAP) Dataset('dsname') ENQ(SHR)' 

until it returned RC =0.  Crude, but effective.

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

Re: How to suppress Message in REXX App (SAMPLE)

[Paul Gilmartin]

On Sun, 3 Jun 2012 17:06:35 +0200, Giovanni Santuz wrote:
>
>RD =RANDOM(1,9)
>HSMDS = 'TWRK.TEMP.D'!!RD
>"HLIST DSNAME('"ODSN"') ODS('"HSMDS"')"
>CALL READ_HSMDS
> 
Is RANDOM() the best way to do this, given that there's a 50%
chance of collision in 372 tries?  Would it be better (and more
informative) to generate a DSN using date/timestamps (despite
a certainty of collision if the script is run twice in one second)?

The real shame here is that DFSMShsm does not support using
a temporary DSN (or z/OS UNIX (USS) file or pipeline) by providing
either an OUTDDNAME or an OUTVOL parameter.

>READ_HSMDS:
>"ALLOC DATASET('"HSMDS"') File(HSMDS) SHR "
>"EXECIO 0 DISKR HSMDS (OPEN"
>"EXECIO * DISKR HSMDS (STEM HSMI."
>"EXECIO 0 DISKR HSMDS (FINIS "

Can't the above 3 commands be collapsed into one (OPEN
is utterly superfluous -- assembler habit?):

"EXECIO * DISKR HSMDS (FINIS STEM HSMI."

>X = MSG(OFF)
>"DELETE '"HSMDS"'"
>X = MSG(ON)
>"FREE DD(HSMDS)"
>RETURN
>
I read in:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2U390/2.6

Title: z/OS V1R12.0 DFSMShsm Managing Your Own Data
Document Number: SC35-0420-09
2.6 HLIST: Listing information from the BCDS and MCDS
...
The HLIST command is a long-running command that can tie up your TSO 
terminal if its output is directed to TERM. 

Should I infer from this that conversely it runs concurrently
in background and does not tie up the terminal  if output is
directed to SYSOUT or ODS?  If so the above EXEC needs a
WAIT to guarantee that the output is complete.  (Or does
ENQ SHR handle this?)

-- gil

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

Re: How to suppress Message in REXX App (SAMPLE)

[Giovanni Santuz]

Am 03.06.2012 04:10, schrieb Shmuel Metz (Seymour J.):

In
,
on 06/02/2012
at 12:02 PM, Itschak Mugzach  said:


Did you try REXX OUTTRAP function?

OUTTRAP catches PUTLINE and PUTGET, not TPUT.


HI
Here a sample to Do a HLIST, and process the info in the  REXX.Proc
Data is written in the STEM HSMI.

ODSN = Name of the  DSN

RD ist a Random number to be able to alloc a Unique file
This is part of a proc that processes > 100.000 Files thru a Batch file

Hope it helps

Giovanni


RD =RANDOM(1,9)
HSMDS = 'TWRK.TEMP.D'!!RD
"HLIST DSNAME('"ODSN"') ODS('"HSMDS"')"
CALL READ_HSMDS


READ_HSMDS:
"ALLOC DATASET('"HSMDS"') File(HSMDS) SHR "
"EXECIO 0 DISKR HSMDS (OPEN"
"EXECIO * DISKR HSMDS (STEM HSMI."
"EXECIO 0 DISKR HSMDS (FINIS "
X = MSG(OFF)
"DELETE '"HSMDS"'"
X = MSG(ON)
"FREE DD(HSMDS)"
RETURN

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

Re: How to suppress Message in REXX App

[John Gilmore]

On 6/3/12, Giovanni Santuz  wrote:
> Am 01.06.2012 18:43, schrieb Lizette Koehler:
>> Cross Posting to IBM Main and TSO-REXX
>>
>>
>> I have a Rexx process that issues the HLIST command.  I have been
>> successful
>> in trapping the output from the HLIST but have an issue when the message
>>
>> ARC0138I is issued.
>>
>> I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
>> etc)
>> I have tried turning off message for that section of the code MSG('OFF')
>>
>> Any yet it keeps getting produced so the user has to keep hitting enter
>> until they are cleared.
>>
>> This message can be overwhelming if my user requests 100's of datasets
>> that
>> do not have an MCDS entry.
>>
>> Does anyone know if this message can be suppressed from a TSO session?
>> IF
>> so, suggestions?
>>
>> Thanks
>>
>> Lizette Koehler
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> HI
> Use  X = MSG(OFF)   before the TSO Comand and X = MSG(ON) after
>
> Giovanni
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>


-- 
John Gilmore, Ashland, MA 01721 - USA

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

Re: How to suppress Message in REXX App

[Giovanni Santuz]

Am 01.06.2012 18:43, schrieb Lizette Koehler:

Cross Posting to IBM Main and TSO-REXX


I have a Rexx process that issues the HLIST command.  I have been successful
in trapping the output from the HLIST but have an issue when the message

ARC0138I is issued.

I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
etc)
I have tried turning off message for that section of the code MSG('OFF')

Any yet it keeps getting produced so the user has to keep hitting enter
until they are cleared.

This message can be overwhelming if my user requests 100's of datasets that
do not have an MCDS entry.

Does anyone know if this message can be suppressed from a TSO session?  IF
so, suggestions?

Thanks

Lizette Koehler

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

HI
Use  X = MSG(OFF)   before the TSO Comand and X = MSG(ON) after

Giovanni

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

Re: How to suppress Message in REXX App

[Shmuel Metz (Seymour J.)]

In
,
on 06/01/2012
   at 03:14 PM, Skip Robinson  said:

>TPUT is an SVC that cannot be intercepted by TSO and therefore 
>cannot be suppressed by TSO.

Actually, it can be intercepted, and the TSO Session Manager does
intercept it. 
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: How to suppress Message in REXX App

[Shmuel Metz (Seymour J.)]

In
,
on 06/02/2012
   at 12:02 PM, Itschak Mugzach  said:

>Did you try REXX OUTTRAP function?

OUTTRAP catches PUTLINE and PUTGET, not TPUT.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: How to suppress Message in REXX App

[Shmuel Metz (Seymour J.)]

In , on 06/01/2012
   at 04:37 PM, Scott Ford  said:

>TPut will go to sysprint or systsprt

No. PUTLINE in batch will go to SYSTSPRT, but not TPUT.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: How to suppress Message in REXX App

[Itschak Mugzach]

You trap the output using a parameter of the HLIST command Did you try REXX
OUTTRAP function?

ITschak

On Fri, Jun 1, 2012 at 7:43 PM, Lizette Koehler wrote:

> Cross Posting to IBM Main and TSO-REXX
>
>
> I have a Rexx process that issues the HLIST command.  I have been
> successful
> in trapping the output from the HLIST but have an issue when the message
>
> ARC0138I is issued.
>
> I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
> etc)
> I have tried turning off message for that section of the code MSG('OFF')
>
> Any yet it keeps getting produced so the user has to keep hitting enter
> until they are cleared.
>
> This message can be overwhelming if my user requests 100's of datasets that
> do not have an MCDS entry.
>
> Does anyone know if this message can be suppressed from a TSO session?  IF
> so, suggestions?
>
> Thanks
>
> Lizette Koehler
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>

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

Re: How to suppress Message in REXX App

[Tony Harminc]

On 1 June 2012 18:14, Skip Robinson  wrote:
> TSO PROFILE command controls messages issued via PUTLINE, which invokes
> TSO services and is therefore suppressible within TSO. TPUT is an SVC that
> cannot be intercepted by TSO and therefore cannot be suppressed by TSO.

Uh, not exactly. While TSO does not "intercept" TPUTs, PROFILE
NOINTERCOM most certainly controls ordinary TPUTs from another address
space. However there is a "high priority" (can't remember the keyword)
option on x-mem TPUT that overrides NOINTERCOM. It requires APF
authorization. So much the worse for the design if the program really
is using this option to force its messages on the poor user.

But I don't know the product in question, and so if the TPUT is coming
from another address space; if it's running in the TSO address space
it can't be suppressed by NOINTERCOM.

Tony H.

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

Re: How to suppress Message in REXX App

[Shmuel Metz (Seymour J.)]

In <026801cd4015$ba6e3cd0$2f4ab670$@mindspring.com>, on 06/01/2012
   at 09:43 AM, Lizette Koehler  said:

>Does anyone know if this message can be suppressed from a TSO
>session?  IF so, suggestions?

Run under Session Manager?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: How to suppress Message in REXX App

[Skip Robinson]

TSO PROFILE command controls messages issued via PUTLINE, which invokes 
TSO services and is therefore suppressible within TSO. TPUT is an SVC that 
cannot be intercepted by TSO and therefore cannot be suppressed by TSO. 

.
.
JO.Skip Robinson
SCE Infrastructure 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:   Scott Ford 
To: IBM-MAIN@bama.ua.edu
Date:   06/01/2012 03:04 PM
Subject:Re: How to suppress Message in REXX App
Sent by:IBM Mainframe Discussion List 



Yes, system

Scott ford
www.identityforge.com

On Jun 1, 2012, at 5:59 PM, Walt Farrell  wrote:

> On Fri, 1 Jun 2012 16:37:51 -0400, Scott Ford  
wrote:
> 
>> TPut will go to sysprint or systsprt
> 
> She's concerned about a TSO session, and there it will go to the 
terminal.
> 
> -- 
> Walt



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

Re: How to suppress Message in REXX App

[Scott Ford]

Yes, system

Scott ford
www.identityforge.com

On Jun 1, 2012, at 5:59 PM, Walt Farrell  wrote:

> On Fri, 1 Jun 2012 16:37:51 -0400, Scott Ford  wrote:
> 
>> TPut will go to sysprint or systsprt
> 
> She's concerned about a TSO session, and there it will go to the terminal.
> 
> -- 
> Walt
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

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

Re: How to suppress Message in REXX App

[Walt Farrell]

On Fri, 1 Jun 2012 16:37:51 -0400, Scott Ford  wrote:

>TPut will go to sysprint or systsprt

She's concerned about a TSO session, and there it will go to the terminal.

-- 
Walt

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

Re: How to suppress Message in REXX App

[Scott Ford]

Lizette,

TPut will go to sysprint or systsprt

Scott ford
www.identityforge.com

On Jun 1, 2012, at 4:16 PM, Lizette Koehler  wrote:

> Scott 
> 
> Yes the output is going to a outdsn
> 
> HLIST DSN('"dsnvar"') MCDS ODS('"tmpdsn"')
> 
> 
> I have set  TSO PROF NOINTERCOM NOPAUSE NOMSGID NOMODE  NOWTPMSG NORECOVER
> 
> I have added the turning off of MSG prior to the HLIST and restore it after 
> HLIST.
> 
> I think the problem as pointed out is a TPUT.  Which means I may not be able 
> to suppress it from the user's session.
> 
> Lizette
> 
> 
> -Original Message-----
>> From: Scott Ford 
>> Sent: Jun 1, 2012 1:03 PM
>> To: IBM-MAIN@bama.ua.edu
>> Subject: Re: How to suppress Message in REXX App
>> 
>> Lizette,
>> 
>> Are you trapping the messages ?
>> 
>> Scott ford
>> www.identityforge.com
>> 
>> On Jun 1, 2012, at 12:43 PM, Lizette Koehler  wrote:
>> 
>>> Cross Posting to IBM Main and TSO-REXX
>>> 
>>> 
>>> I have a Rexx process that issues the HLIST command.  I have been successful
>>> in trapping the output from the HLIST but have an issue when the message
>>> 
>>> ARC0138I is issued.
>>> 
>>> I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
>>> etc)
>>> I have tried turning off message for that section of the code MSG('OFF')
>>> 
>>> Any yet it keeps getting produced so the user has to keep hitting enter
>>> until they are cleared.
>>> 
>>> This message can be overwhelming if my user requests 100's of datasets that
>>> do not have an MCDS entry.
>>> 
>>> Does anyone know if this message can be suppressed from a TSO session?  IF
>>> so, suggestions?
>>> 
>>> Thanks
>>> 
>>> Lizette Koehler
>>> 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

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

Re: How to suppress Message in REXX App

[Dennis Trojak]

Liz,
 Since you are doing this within a REXX why not issue a LISTC command on the 
DSN first with the VOL parameter and see if the VOLSER is MIGRAT before you 
issue the HLIST command? That way you know the dataset is truly migrated.
Dennis

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Lizette Koehler
Sent: Friday, June 01, 2012 3:16 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: How to suppress Message in REXX App

Scott 

Yes the output is going to a outdsn

HLIST DSN('"dsnvar"') MCDS ODS('"tmpdsn"')


I have set  TSO PROF NOINTERCOM NOPAUSE NOMSGID NOMODE  NOWTPMSG NORECOVER

I have added the turning off of MSG prior to the HLIST and restore it after 
HLIST.

I think the problem as pointed out is a TPUT.  Which means I may not be able to 
suppress it from the user's session.

Lizette


-Original Message-
>From: Scott Ford 
>Sent: Jun 1, 2012 1:03 PM
>To: IBM-MAIN@bama.ua.edu
>Subject: Re: How to suppress Message in REXX App
>
>Lizette,
>
>Are you trapping the messages ?
>
>Scott ford
>www.identityforge.com
>
>On Jun 1, 2012, at 12:43 PM, Lizette Koehler  wrote:
>
>> Cross Posting to IBM Main and TSO-REXX
>> 
>> 
>> I have a Rexx process that issues the HLIST command.  I have been 
>> successful in trapping the output from the HLIST but have an issue 
>> when the message
>> 
>> ARC0138I is issued.
>> 
>> I have tried turning off all of the TSO PROF functions (MSGID, 
>> INTERCOM,
>> etc)
>> I have tried turning off message for that section of the code 
>> MSG('OFF')
>> 
>> Any yet it keeps getting produced so the user has to keep hitting 
>> enter until they are cleared.
>> 
>> This message can be overwhelming if my user requests 100's of 
>> datasets that do not have an MCDS entry.
>> 
>> Does anyone know if this message can be suppressed from a TSO 
>> session?  IF so, suggestions?
>> 
>> Thanks
>> 
>> Lizette Koehler
>>

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

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

Re: How to suppress Message in REXX App

[Lizette Koehler]

Scott 

Yes the output is going to a outdsn

HLIST DSN('"dsnvar"') MCDS ODS('"tmpdsn"')


I have set  TSO PROF NOINTERCOM NOPAUSE NOMSGID NOMODE  NOWTPMSG NORECOVER

I have added the turning off of MSG prior to the HLIST and restore it after 
HLIST.

I think the problem as pointed out is a TPUT.  Which means I may not be able to 
suppress it from the user's session.

Lizette


-Original Message-
>From: Scott Ford 
>Sent: Jun 1, 2012 1:03 PM
>To: IBM-MAIN@bama.ua.edu
>Subject: Re: How to suppress Message in REXX App
>
>Lizette,
>
>Are you trapping the messages ?
>
>Scott ford
>www.identityforge.com
>
>On Jun 1, 2012, at 12:43 PM, Lizette Koehler  wrote:
>
>> Cross Posting to IBM Main and TSO-REXX
>> 
>> 
>> I have a Rexx process that issues the HLIST command.  I have been successful
>> in trapping the output from the HLIST but have an issue when the message
>> 
>> ARC0138I is issued.
>> 
>> I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
>> etc)
>> I have tried turning off message for that section of the code MSG('OFF')
>> 
>> Any yet it keeps getting produced so the user has to keep hitting enter
>> until they are cleared.
>> 
>> This message can be overwhelming if my user requests 100's of datasets that
>> do not have an MCDS entry.
>> 
>> Does anyone know if this message can be suppressed from a TSO session?  IF
>> so, suggestions?
>> 
>> Thanks
>> 
>> Lizette Koehler
>>

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

Re: How to suppress Message in REXX App

[Scott Ford]

Lizette,

Are you trapping the messages ?

Scott ford
www.identityforge.com

On Jun 1, 2012, at 12:43 PM, Lizette Koehler  wrote:

> Cross Posting to IBM Main and TSO-REXX
> 
> 
> I have a Rexx process that issues the HLIST command.  I have been successful
> in trapping the output from the HLIST but have an issue when the message
> 
> ARC0138I is issued.
> 
> I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
> etc)
> I have tried turning off message for that section of the code MSG('OFF')
> 
> Any yet it keeps getting produced so the user has to keep hitting enter
> until they are cleared.
> 
> This message can be overwhelming if my user requests 100's of datasets that
> do not have an MCDS entry.
> 
> Does anyone know if this message can be suppressed from a TSO session?  IF
> so, suggestions?
> 
> Thanks
> 
> Lizette Koehler
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

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

Re: How to suppress Message in REXX App

[Ed Gould]

Gil:

Maybe I am not understanding of your complaint.
The ARC message is sent to you as *YOU* requested some function from  
HSM.
HLIST for example is your request to DFHSM to list something (usually  
a DSN) and DFHSM is responding to your request.

So please explain why you are objecting to receiving the message?

Ed


On Jun 1, 2012, at 2:40 PM, Paul Gilmartin wrote:


On Fri, 1 Jun 2012 13:27:54 -0500, McKown, John wrote:

I don't know about that message in particular, but I know that the  
HSM started task often issues message via a directed TPUT having  
an option to deliver it to the userid which issued the HSM  
command. Similar to what the z/OS "SEND" commands does when sent  
by another TSO user or operator command. I don't know of any way  
to suppress it. Perhaps TSO PROFILE NOINTERCOM but I'm not in a  
position to try it. Makes me madder than you-know-where. Sometimes  
I'd like to strangle IBM developers.



Than behavior is _so_ 20th century.  The function needs to
be redesigned, at the very least to send the message to the
address space that requested the operation.  But IBM doesn't
care enough to do it right.

-- gil

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


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

Re: How to suppress Message in REXX App

[Paul Gilmartin]

On Fri, 1 Jun 2012 13:27:54 -0500, McKown, John wrote:

>I don't know about that message in particular, but I know that the HSM started 
>task often issues message via a directed TPUT having an option to deliver it 
>to the userid which issued the HSM command. Similar to what the z/OS "SEND" 
>commands does when sent by another TSO user or operator command. I don't know 
>of any way to suppress it. Perhaps TSO PROFILE NOINTERCOM but I'm not in a 
>position to try it. Makes me madder than you-know-where. Sometimes I'd like to 
>strangle IBM developers.
> 
Than behavior is _so_ 20th century.  The function needs to
be redesigned, at the very least to send the message to the
address space that requested the operation.  But IBM doesn't
care enough to do it right.

-- gil

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

Re: How to suppress Message in REXX App

[Stocker, Herman]

Lizette,

MSGID only places the ID in the message.

In the TSO PROFILE have you tried NOWTPMSG
NOWTPMSG - SPECIFIES THE USER DOES NOT WISH TO RECEIVE WRITE TO
   PROGRAMMER MESSAGES AT HIS TERMINAL

I have not tested it but it may do what you want.

Regards,
Herman Stocker

It is impossible to make anything foolproof, because fools are so ingenious.
 -- Robert Heinlein


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Lizette Koehler
Sent: Friday, June 01, 2012 12:44 PM
To: IBM-MAIN@bama.ua.edu
Subject: How to suppress Message in REXX App

Cross Posting to IBM Main and TSO-REXX


I have a Rexx process that issues the HLIST command.  I have been successful in 
trapping the output from the HLIST but have an issue when the message

ARC0138I is issued.

I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
etc)
I have tried turning off message for that section of the code MSG('OFF')

Any yet it keeps getting produced so the user has to keep hitting enter until 
they are cleared.

This message can be overwhelming if my user requests 100's of datasets that do 
not have an MCDS entry.

Does anyone know if this message can be suppressed from a TSO session?  IF so, 
suggestions?

Thanks

Lizette Koehler

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

 ---

The sender believes that this E-mail and any attachments were free of any
virus, worm, Trojan horse, and/or malicious code when sent. This message and
its attachments could have been infected during transmission. By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action about viruses and
other defects. The sender's employer is not liable for any loss or damage
arising in any way from this message or its attachments.

 ---

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

Re: How to suppress Message in REXX App

[McKown, John]

I don't know about that message in particular, but I know that the HSM started 
task often issues message via a directed TPUT having an option to deliver it to 
the userid which issued the HSM command. Similar to what the z/OS "SEND" 
commands does when sent by another TSO user or operator command. I don't know 
of any way to suppress it. Perhaps TSO PROFILE NOINTERCOM but I'm not in a 
position to try it. Makes me madder than you-know-where. Sometimes I'd like to 
strangle IBM developers.

-- 
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler
> Sent: Friday, June 01, 2012 11:44 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: How to suppress Message in REXX App
> 
> Cross Posting to IBM Main and TSO-REXX
> 
> 
> I have a Rexx process that issues the HLIST command.  I have 
> been successful
> in trapping the output from the HLIST but have an issue when 
> the message
> 
> ARC0138I is issued.
> 
> I have tried turning off all of the TSO PROF functions 
> (MSGID, INTERCOM,
> etc)
> I have tried turning off message for that section of the code 
> MSG('OFF')
> 
> Any yet it keeps getting produced so the user has to keep 
> hitting enter
> until they are cleared.
> 
> This message can be overwhelming if my user requests 100's of 
> datasets that
> do not have an MCDS entry.
> 
> Does anyone know if this message can be suppressed from a TSO 
> session?  IF
> so, suggestions?
> 
> Thanks
> 
> Lizette Koehler
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> 

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

How to suppress Message in REXX App

[Lizette Koehler]

Cross Posting to IBM Main and TSO-REXX


I have a Rexx process that issues the HLIST command.  I have been successful
in trapping the output from the HLIST but have an issue when the message

ARC0138I is issued.

I have tried turning off all of the TSO PROF functions (MSGID, INTERCOM,
etc)
I have tried turning off message for that section of the code MSG('OFF')

Any yet it keeps getting produced so the user has to keep hitting enter
until they are cleared.

This message can be overwhelming if my user requests 100's of datasets that
do not have an MCDS entry.

Does anyone know if this message can be suppressed from a TSO session?  IF
so, suggestions?

Thanks

Lizette Koehler

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