There used to be a site that had caricatures of SHARE folk, but I can't find
it. This is from SHARE blog in Seattle.
https://www.share.org/p/bl/et/blogaid=341
In a message dated 7/3/2018 7:46:55 AM Central Standard Time,
rpomm...@sfgmembers.com writes:
I dunno, can't be age. I've seen
ROR : IGD01022I)
Making the wee joke. Ha ha.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, July 3, 2018 7:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Formatting (was: JCL ERROR : IGD01022I)
The E
Making the wee joke. Ha ha.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, July 3, 2018 7:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Formatting (was: JCL ERROR : IGD01022I)
The Enya
Mainframe Discussion List on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Monday, July 2, 2018 3:28 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Formatting (was: JCL ERROR : IGD01022I)
On Mon, 2 Jul 2018 14:55:33 -0400, Edward Finnell wrote:
>I looked at the
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Formatting (was: JCL ERROR : IGD01022I)
There you go using them dang Unicode characters again.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent: Monday, July 2, 2018 3:06 PM
Subject: Re: Formatting (was: JCL ERROR : IGD01022I)
On 7/2/2018 11:55 AM, Edward Finnell wrote:
> I looked at the archives and Senior Jaffe's post appears correctly formatted.
> It has plain/text and proportional font.
Was this intended to be "Señor Jaffe?" Or was it a c
Sort of an amalgamation from long ago posts. Just trying to dodge the lightning
bolts. Guess it could mean senior techy too.
In a message dated 7/2/2018 5:06:42 PM Central Standard Time,
edja...@phoenixsoftware.com writes:
Was this intended to be "Señor Jaffe?" Or was it a comment on my age
There you go using them dang Unicode characters again.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent: Monday, July 2, 2018 3:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Formatting (was: JCL ERROR
On 7/2/2018 11:55 AM, Edward Finnell wrote:
I looked at the archives and Senior Jaffe's post appears correctly formatted.
It has plain/text and proportional font.
Was this intended to be "Señor Jaffe?" Or was it a comment on my age
and/or experience? ;-)
--
Phoenix Software International
Definitely an admin question. The other interlocutor is the distribution server
that takes the listserv post and spews it out to the subscribers. It may be
munging for compression or just that's all it knows.
In a message dated 7/2/2018 2:28:25 PM Central Standard Time,
I looked at the archives and Senior Jaffe's post appears correctly formatted.
It has plain/text and proportional font.
AFAIK, I've never had an issue posting code fragments on any list. I'm
gonna experiment with one right now randomly taken from our
equ...@listserv.ua.edu>
Sent: Monday, July 2, 2018 2:16 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Formatting (was: JCL ERROR : IGD01022I)
(Yaay! You're no longer using koi8-r!)
On Mon, 2 Jul 2018 17:06:08 +, Seymour J Metz wrote:
>Implementing any new RFC is a big order. If the mail clients on
(Yaay! You're no longer using koi8-r!)
On Mon, 2 Jul 2018 17:06:08 +, Seymour J Metz wrote:
>Implementing any new RFC is a big order. If the mail clients on both ends
>implement RFC 3676, then cut-and-paste works. If a brain dead application
>simply slaps in format=flowed without
:35 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Formatting (was: JCL ERROR : IGD01022I)
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 prope
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
smetz3
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Saturday, June 30, 2018 8:53 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Formatting (was: JCL ERROR : IGD01022I)
On 2018-06-29, at 13:19:38, Ed Jaffe wrote:
&g
On 2018-06-29, at 13:19:38, Ed Jaffe wrote:
> On 6/29/2018 9:00 AM, Lizette Koehler wrote:
>> I cannot read the JCL listing. Please put at least 3 spaces when pasting
>> JCL into email
>>
>> For example without spaces
> [snip]
>
> The formatting problem is not due to a lack of leading spaces.
On 6/29/2018 9:00 AM, Lizette Koehler wrote:
I cannot read the JCL listing. Please put at least 3 spaces when pasting JCL
into email
For example without spaces
[snip]
The formatting problem is not due to a lack of leading spaces. The
problem is trailing whitespace. With all trailing spaces
n List On Behalf Of
> Jeremy Nicoll
> Sent: Friday, June 29, 2018 9:46 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JCL ERROR : IGD01022I
>
> On Fri, 29 Jun 2018, at 15:42, esmie moo wrote:
>
> > Below is my JCL.
> > /*
On Fri, 29 Jun 2018, at 15:42, esmie moo wrote:
> Below is my JCL.
> /* //STEP1
> EXEC PGM=IEFBR14 //SYSPRINT DD
> SYSOUT=* //SYSIN DD DUMMY
>
Problem solved The SMS rule was automatically allocating the dsn on virtual
tape instead of dasd.
On Friday, June 29, 2018, 10:46:55 a.m. EDT, esmie moo
<012780d99c7b-dmarc-requ...@listserv.ua.edu> wrote:
Gentle Readers
I am encountering allocating a dsn on a non-sms dasd. I
name
Option 7 in ISMF - look for TEST
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> esmie moo
> Sent: Friday, June 29, 2018 7:43 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: JCL ERROR : IGD01022I
>
> Gentle Readers
> I
Gentle Readers
I am encountering allocating a dsn on a non-sms dasd. I received the following
error:
IGD01022I EITHER A NON-LIBRARY VOLUME IS SPECIFIED OR
THE VOLUME SPECIFIED IS NOT IN LIBRARY DTM1455I 2018.180
10:25:54 Job IEFBR14D failed, JCL Error
Below is my JCL.
/*
23 matches
Mail list logo
