On 2018-07-01, at 19:03:32, Don Poitras wrote:
> ---
>> Mime-Version: 1.0
>> Content-Type: text/plain; charset=koi8-r; format=flowed
>> Content-Transfer-Encoding: 8bit
> ---
> I'm guessing Ed didn't intend to use a Russion character set. :) If that
> wasn't what
> was used in the email, then it
That is quite repulsive.
On Sun, Jul 1, 2018 at 2:59 PM Gord Tomlin
wrote:
> On 2018-06-30 21:39, Beverly Caldwell wrote:
> > Unfortunately people with names like yours...
>
> Admins, can we take care of this please?
>
> --
>
> Regards, Gord Tomlin
> Action Software International
> (a division
On Sun, 1 Jul 2018 21:03:32 -0400, Don Poitras wrote:
>I read IBM-MAIN from a newsreader. The rexx script had lots of the blanks
>repaced with something else. Saving the file and looking at the headers,
>I see:
>
>---
>> Mime-Version: 1.0
>> Content-Type: text/plain; charset=koi8-r;
My typed in lines look OK. These lines are copy/pasted from Notepad.
line 1 pasted in
line 2 pasted in
line 3 pasted in
.
.
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
I read IBM-MAIN from a newsreader. The rexx script had lots of the blanks
repaced with something else. Saving the file and looking at the headers,
I see:
---
> Mime-Version: 1.0
> Content-Type: text/plain; charset=koi8-r; format=flowed
> Content-Transfer-Encoding: 8bit
---
I'm guessing Ed
This code looks fine. My experience in posting to IBM-MAIN is that spaces at
the beginning *or end* of a line allows the data to look fine. But truncating
both leading and trailing spaces causes the List processor to flow lines up to
the next 'break', which may be a totally blank line. I try to
On 7/1/2018 11:39 AM, Seymour J Metz wrote:
I consider RFC 3676 an abomination, totally unsuitable for posting code
samples.
Why? Do you know of any case where a properly behaving mail client mangles code
properly formatted with format=flowed?
AFAIK, I've never had an issue posting code
On Sun, 1 Jul 2018 18:39:02 +, Seymour J Metz wrote:
>> I consider RFC 3676 an abomination, totally unsuitable for posting code
>> samples.
>
>Why? Do you know of any case where a properly behaving mail client mangles
>code properly formatted with format=flowed?
>
"properly formatted" is a
+1
בתאריך יום א׳, 1 ביולי 2018, 22:59, מאת Gord Tomlin <
gt.ibm.li...@actionsoftware.com>:
> On 2018-06-30 21:39, Beverly Caldwell wrote:
> > Unfortunately people with names like yours...
>
> Admins, can we take care of this please?
>
> --
>
> Regards, Gord Tomlin
> Action Software
On Sun, 1 Jul 2018 13:11:27 -0400, Hobart Spitz wrote:
>)Why don't we just skip the JCL, and write our jobs in REXX? The two
>
>Here, here!! Actually, there is one thing that is critical to retiring
>JCL. It's a host command that allows a REXX program to list and wait for
>all it's datasets
On 2018-06-30 21:39, Beverly Caldwell wrote:
Unfortunately people with names like yours...
Admins, can we take care of this please?
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support:
> I consider RFC 3676 an abomination, totally unsuitable for posting code
> samples.
Why? Do you know of any case where a properly behaving mail client mangles code
properly formatted with format=flowed?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
)Why don't we just skip the JCL, and write our jobs in REXX? The two
Here, here!! Actually, there is one thing that is critical to retiring
JCL. It's a host command that allows a REXX program to list and wait for
all it's datasets and their enqueues to be available. This is not trivial,
so
13 matches
Mail list logo
