Re: WTO and IEF170I message

2022-10-18 Thread Charles Mills
Yikes indeed!

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Abell
Sent: Tuesday, October 18, 2022 11:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WTO and IEF170I message

And she was deemed to possibly your next President.  YIKES

John T. Abell   
Tel:800-295-7608Option 4
President 
International:  1-416-593-5578  Option 4
E-mail:  john.ab...@intnlsoftwareproducts.com
Fax:800-295-7609

International:  1-416-593-5579


International Software Products
www.ispinfo.com


This email may contain confidential and privileged material for the sole use of 
the intended recipient(s). Any review, use, retention, distribution or 
disclosure by others is strictly prohibited. If you are not the intended 
recipient (or authorized to receive on behalf of the named recipient), please 
contact the sender by reply email and delete all copies of this message. 
Also,email is susceptible to data corruption, interception, 
tampering, unauthorized amendment and viruses. We only send and receive emails 
on the basis that we are not liable for any such corruption, interception, 
tampering, amendment or viruses or any consequence thereof.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Pierre Fichaud
Sent: Tuesday, October 18, 2022 2:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: WTO and IEF170I message

I issue a plain WTO :wto   'This is a message'
I also issue a WTO  :wto   text=dsa_wtotext,mf=(e,dsa_wtoarea)

In both cases the WTO appears in the SDSF LOG.

But I also get an IEF170I message for each WTO no matter the flavor.

IEF170I 3  This is a message

A WTO or WTOR macro requested a write-to-programmer (WTP) operation. The system 
was unable to complete WTP processing due to an error

3 means "The system issued the PUT macro to a system message data set, but 
failed."

The code runs in an exit but since SVCs are allowed in the exit, the code must 
execute in TCB mode.

Is there something in the WTO parameters that causes the IEF170 message to 
disappear ?
Maybe a combination of MCSFLAG, DESC and ROUTCDE ?

Thanks in advance, Pierre.

--
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: WTO and IEF170I message

2022-10-18 Thread Binyamin Dissen
As you have not specified ROUTCDE, CONSOL** takes over. Probably includes 11.

On Tue, 18 Oct 2022 13:37:35 -0500 Pierre Fichaud  wrote:

:>I issue a plain WTO :wto   'This is a message'
:>I also issue a WTO  :wto   text=dsa_wtotext,mf=(e,dsa_wtoarea)

:>In both cases the WTO appears in the SDSF LOG.

:>But I also get an IEF170I message for each WTO no matter the flavor.

:>IEF170I 3  This is a message

:>A WTO or WTOR macro requested a write-to-programmer (WTP) operation. The 
system was unable to complete
:>WTP processing due to an error

:>3 means "The system issued the PUT macro to a system message data set, but 
failed."

:>The code runs in an exit but since SVCs are allowed in the exit, the code 
must execute in TCB mode.

:>Is there something in the WTO parameters that causes the IEF170 message to 
disappear ?
:>Maybe a combination of MCSFLAG, DESC and ROUTCDE ?

--
Binyamin Dissen 
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

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


Re: WTO and IEF170I message

2022-10-18 Thread John Abell
And she was deemed to possibly your next President.  YIKES

John T. Abell   
Tel:800-295-7608Option 4
President 
International:  1-416-593-5578  Option 4
E-mail:  john.ab...@intnlsoftwareproducts.com
Fax:800-295-7609

International:  1-416-593-5579


International Software Products
www.ispinfo.com


This email may contain confidential and privileged material for the sole use of 
the intended recipient(s). Any review, use, retention, distribution or 
disclosure by others is strictly prohibited. If you are not the intended 
recipient (or authorized to receive on behalf of the named recipient), please 
contact the sender by reply email and delete all copies of this message. 
Also,email is susceptible to data corruption, interception, 
tampering, unauthorized amendment and viruses. We only send and receive emails 
on the basis that we are not liable for any such corruption, interception, 
tampering, amendment or viruses or any consequence thereof.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Pierre Fichaud
Sent: Tuesday, October 18, 2022 2:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: WTO and IEF170I message

I issue a plain WTO :wto   'This is a message'
I also issue a WTO  :wto   text=dsa_wtotext,mf=(e,dsa_wtoarea)

In both cases the WTO appears in the SDSF LOG.

But I also get an IEF170I message for each WTO no matter the flavor.

IEF170I 3  This is a message

A WTO or WTOR macro requested a write-to-programmer (WTP) operation. The system 
was unable to complete WTP processing due to an error

3 means "The system issued the PUT macro to a system message data set, but 
failed."

The code runs in an exit but since SVCs are allowed in the exit, the code must 
execute in TCB mode.

Is there something in the WTO parameters that causes the IEF170 message to 
disappear ?
Maybe a combination of MCSFLAG, DESC and ROUTCDE ?

Thanks in advance, Pierre.

--
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


WTO and IEF170I message

2022-10-18 Thread Pierre Fichaud
I issue a plain WTO :wto   'This is a message'
I also issue a WTO  :wto   text=dsa_wtotext,mf=(e,dsa_wtoarea)

In both cases the WTO appears in the SDSF LOG.

But I also get an IEF170I message for each WTO no matter the flavor.

IEF170I 3  This is a message

A WTO or WTOR macro requested a write-to-programmer (WTP) operation. The system 
was unable to complete
WTP processing due to an error

3 means "The system issued the PUT macro to a system message data set, but 
failed."

The code runs in an exit but since SVCs are allowed in the exit, the code must 
execute in TCB mode.

Is there something in the WTO parameters that causes the IEF170 message to 
disappear ?
Maybe a combination of MCSFLAG, DESC and ROUTCDE ?

Thanks in advance, Pierre.

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


Re: A Million Years

2022-10-18 Thread Paul Gilmartin
On Tue, 18 Oct 2022 09:55:22 -0400, Mike Shaw wrote:

>We use IEBDG to generate separator records between concatenated XMIT files
>
Thanks.

>for our LINKLIB, panels, msgs, etc. That sandwich then gets converted 
>printable EBCDIC and imbedded within REXX code that will self-unpack those
>
"uuencode -m" might be good for that'.  I've done POC but never used it
in practice.  XMIT in instream JCL suffers the risk that there is no digraph
safe to use in DLM=.

Rexx sadly lacks an instream data facility.   I've faked it with
sourceline() fetching from comment text.

>XMIT files (via TSO/E RECEIVEs) when invoked on z/OS.

-- 
gil

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


Re: A Million Years

2022-10-18 Thread Mike Shaw
We use IEBDG to generate separator recordS between concatenated XMIT files
for our LINKLIB, panels, msgs, etc. That sandwich then gets converted to
printable EBCDIC and imbedded within REXX code that will self-unpack those
XMIT files (via TSO/E RECEIVEs) when invoked on z/OS.

Mike



On Tue, Oct 18, 2022 at 9:11 AM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:

> On Tue, 18 Oct 2022 05:23:24 -0400, Mike Shaw wrote:
>
> >We use IEBUPDTE for Assembler source change application. SUPERC can
> compare
> >two source programs and generate a Delta file in IEBUPDTE format.
> >
> But, dammit, the UPDMVS8 option requires that both comparands have
> valid sequence numbers.  UPDCMA8 requires only that the OLD
> comparand have valid sequence numbers.  Why!?
>
> I wrote a script to use UPDCMS8 (not hard to reverse-engineer) and
> convert to IEBUPDTE format, supporting undisciplined coders who
> used non-numbering editors and delivering numbered ++MAC elememts
> to customers.
>
> >We even use IEBDG as part of a process when packaging our product elements
> >for customer download.
> >
> Details?  I'm unfamiliar with IEBDG.  I thought it was for generating test
> data.
>
> --
> gil
>
> --
> 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: A Million Years

2022-10-18 Thread Paul Gilmartin
On Tue, 18 Oct 2022 05:23:24 -0400, Mike Shaw wrote:

>We use IEBUPDTE for Assembler source change application. SUPERC can compare
>two source programs and generate a Delta file in IEBUPDTE format.
> 
But, dammit, the UPDMVS8 option requires that both comparands have
valid sequence numbers.  UPDCMA8 requires only that the OLD
comparand have valid sequence numbers.  Why!?

I wrote a script to use UPDCMS8 (not hard to reverse-engineer) and
convert to IEBUPDTE format, supporting undisciplined coders who
used non-numbering editors and delivering numbered ++MAC elememts
to customers.

>We even use IEBDG as part of a process when packaging our product elements
>for customer download.
>
Details?  I'm unfamiliar with IEBDG.  I thought it was for generating test data.

-- 
gil

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


Re: z16 ETS setup question - where's the best documentation?

2022-10-18 Thread Ambros, Thomas
Perfect, thank you!  

Thomas Ambros
zEnterprise Operating Systems
zEnterprise Systems Management
518-436-6433

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Tom 
Brennan
Sent: Monday, October 17, 2022 18:26
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z16 ETS setup question - where's the best documentation?

WARNING: This email originated externally. Exercise caution. Think before 
clicking links or opening attachments.


On a z16 I'm involved with I noticed the Customized Planning Aid has a section 
on ETS, including this paragraph:

"External Time Source (ETS) IP network considerations: For redundancy and 
resiliency, The IP addresses ETS1 and ETS2 must be configured on different 
subnets. When planning the Ethernet based External Time Source
   network, it is required that two separate subnets corresponding to
ETS1and ETS2 are routable to the desired NTP/PTP time source(s)."

And maybe there's more in that chapter that might help.

To get the planning aid (if you don't know), logon to Resource Link, go to the 
z16 section, find "Customized planning aids" and there you have to order the 
document for your machine and download it an hour or so later.

On 10/17/2022 1:03 PM, Ambros, Thomas wrote:
> We've been looking but haven't been finding.
>
> What has us puzzled is the ETS/STP interface setup on the SE.  The machine is 
> on a /24 vlan.  If we try to define each ETS LAN Adapter with an IP address 
> and interface subnet mask where the IP addresses are in the same subnet there 
> is an address conflict and the second configuration can't be saved.  So we 
> defined subnet masks that worked as a subset of the /24 vlan and keeping the 
> two IP addresses in their own range we were able to save the ETS LAN Adapter 
> configs:
>
> ETS1 10.xx.xx.2 mask 255.255.255.0, ETS2 10.xx.xx.3 mask 255.255.255.0, 
> conflict.
>
> ETS1 10.xx.xx.2 mask 255.255.255.192, ETS2 10.xx.xx.66 mask 255.255.255.192, 
> no conflict.
>
> That sort of makes sense.   I probably will go back in and change the subnet 
> mask so we move the second IP address nearer the first just to be tidy but it 
> isn't necessary because there's nothing on that entire vlan except the z 
> machines.
>
> However, there is a single selection for the default gateway - you can choose 
> ETS1 or ETS2.  It made sense that we'd use ETS1 and the default gateway of 
> 10.xx.xx.1 which matches up to the vlan.  That works.  Just for fun we 
> changed off that definition and sure enough the STP network's ETS 
> connectivity test failed.Default gateway must match the vlan.
>
> The single interface for the default gateway leaves us puzzled.  If ETS1 
> fails for some reason, we think we're going to have to go in and reconfigure 
> ETS2 to maintain our timer network.  We can't be thinking right.
>
> Has anybody encountered good documentation on the setup, better than Redbooks 
> like the Server Time Protocol setup guide that mention in passing that things 
> have changed but don't specify how?  The z16 Tech Guide doesn't appear to 
> have any good info, either, unless I am totally overlooking it.
>
> Thomas Ambros
>
>
>
>
> KeyCorp Public
>
> This communication may contain privileged and/or confidential information. It 
> is intended solely for the use of the addressee. If you are not the intended 
> recipient, you are strictly prohibited from disclosing, copying, distributing 
> or using any of this information. If you received this communication in 
> error, please contact the sender immediately and destroy the material in its 
> entirety, whether electronic or hard copy. This communication may contain 
> nonpublic personal information about consumers subject to the restrictions of 
> the Gramm-Leach-Bliley Act. You may not directly or indirectly reuse or 
> redisclose such information for any purpose other than to provide the 
> services for which you are receiving the information.
>
> 127 Public Square, Cleveland, OH 44114
>
> If you prefer not to receive future e-mail offers for products or services 
> from Key, send an email to mailto:dnereque...@key.com with 'No Promotional 
> E-mails' in the SUBJECT line.
>
> --
> 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: A Million Years

2022-10-18 Thread Mike Shaw
We use IEBUPDTE for Assembler source change application. SUPERC can compare
two source programs and generate a Delta file in IEBUPDTE format.

We even use IEBDG as part of a process when packaging our product elements
for customer download.

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.

On Mon, Oct 17, 2022, 3:46 PM Seymour J Metz  wrote:

> Yes, but I doubt that it sees much use. As batch update programs go it's
> pretty basic.
>
> 
> From: IBM Mainframe Discussion List  on behalf
> of Bill Johnson <0047540adefe-dmarc-requ...@listserv.ua.edu>
> Sent: Monday, October 17, 2022 3:32 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: A Million Years
>
> Is IEBUPDTE still around? I know it could change strings but had limits
> regarding record length.
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Monday, October 17, 2022, 2:24 PM, Steve Beaver 
> wrote:
>
> A million years ago the  was an IBM Batch Utility to change strings
>
> In a PDS.
>
>
>
> Does anyone remember the name of that utility?
>
>
> --
> 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
>

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