Re: [External] Re: Formatting (was: JCL ERROR : IGD01022I)
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 pictures of you. Don't look like you could be a year over 35!! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Formatting (was: JCL ERROR : IGD01022I)
Agreed - the only thing that would be challenging is remembering that instead of executing the program at the top of the allocations that in REXX the allocations must come first. -- Lionel B. Dyck (Contractor) < Mainframe Systems Programmer - RavenTek Solution Partners -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Tuesday, July 03, 2018 9:51 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Formatting (was: JCL ERROR : 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 Enya is perfectly valid in ISO-1 and ISO-15. Would you rather he wrote it as sennor? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Charles Mills Sent: Monday, July 2, 2018 6:24 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Formatting (was: JCL ERROR : IGD01022I) There you go using them dang Unicode characters again. -- 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: Formatting (was: JCL ERROR : 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 Enya is perfectly valid in ISO-1 and ISO-15. Would you rather he wrote it as sennor? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Charles Mills Sent: Monday, July 2, 2018 6:24 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Formatting (was: JCL ERROR : IGD01022I) There you go using them dang Unicode characters again. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Formatting (was: JCL ERROR : IGD01022I)
Is there an "RFC compliant" profile option for LISTSERV? Is that 9A regardless of charset? WTF is 9A in the charset it used? Was this an individual e-mail or digest? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM 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 archives and Senior Jaffe's post appears correctly formatted. >It has plain/text and proportional font. > In that post of Senior Jaffe's as it was initially distributed to me by LISTSERV, all sequences of multiple blanks were replaced by one fewer x'9A' and one x'20'. Later, I retrieved the same message with a GETPOST command to LISTSERV and in the same mail reader all the blanks were blanks. They can't both be right. At best, LISTSERV's behavior is inconsistent. But how can I generate an SR to L-Soft? I'm not the customer and Darren is inactive. (Proportional/mono font is selectable in LISTSERV Preferences.) -- 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: Formatting (was: JCL ERROR : IGD01022I)
The Enya is perfectly valid in ISO-1 and ISO-15. Would you rather he wrote it as sennor? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Charles Mills Sent: Monday, July 2, 2018 6:24 PM 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 To: IBM-MAIN@LISTSERV.UA.EDU 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 comment on my age and/or experience? ;-) -- 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: [External] Re: Formatting (was: JCL ERROR : IGD01022I)
I dunno, can't be age. I've seen pictures of you. Don't look like you could be a year over 35!! Rex -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 : 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 comment on my age and/or experience? ;-) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Formatting (was: JCL ERROR : IGD01022I)
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 and/or experience? ;-) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 To: IBM-MAIN@LISTSERV.UA.EDU 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 comment on my age and/or experience? ;-) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 comment on my age and/or experience? ;-) -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Formatting (was: JCL ERROR : IGD01022I)
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, 000433f07816-dmarc-requ...@listserv.ua.edu writes: Later, I retrieved the same message with a GETPOST command to LISTSERV and in the same mail reader all the blanks were blanks. They can't both be right. At best, LISTSERV's behavior is inconsistent. But how can I generate an SR to L-Soft? I'm not the customer and Darren is inactive. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Formatting (was: JCL ERROR : IGD01022I)
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 local REXX library. What am I doing wrong? (Or right?) /* REXX */ TSMRMM: address tso /* trace I */ "bpxbatch sh dsmadmc -id=mvs60 -pa=xx -displ=tab", /* "q volhist begindate=TODAY-1 begintime=15:00:00" */ , /* "enddate=TODAY-1 endtime=23:00:00" */ , "q volhist begindate=today" , "> /tmp/tsmrmm.qvolhist" if rc <> 0 then exit 8 "allocate dd(tsmrpt) path('/tmp/tsmrmm.qvolhist')", "recfm(v) lrecl(1024) filedata(text) reuse" if rc <> 0 then exit 8 volcount = 0 In a message dated 7/2/2018 1:31:00 PM Central Standard Time, sme...@gmu.edu writes: AFAIK, I have never used KOI8-R; I can't speak to what m$ outhouse may have done behind my back. Maybe it copied the charset from the message I was responding to? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Formatting (was: JCL ERROR : IGD01022I)
AFAIK, I have never used KOI8-R; I can't speak to what m$ outhouse may have
done behind my back. Maybe it copied the charset from the message I was
responding to?
Do you have human beings doing had encoding of messages? If not, then I'm
obviously talking about software.
Alas, while I know of validators for HTML and CSS, I don't know of any for
e-mail.
Cut-and-paste is beyond the scope of any RFC. However, the considerations are
pretty clear; if the text has a New Line (LF for Eunix, CRLF for windows) then
use a hard NL; if you split due to length, use a soft NL. Follow that and the
rules for space stuffing and you get the code intact at the other end. Break
them and all bets are off.
If the receiver does not support F=F then he will get extraneous line breaks; I
can't imagine what idiocy would cause extraneous line wrapping.
BTW, the webmail application for this e-mail account uses m$ lookout, and I
would not be surprised by any RFC violation that turns up.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@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 both ends
>implement RFC 3676, then cut-and-paste works. If a brain dead application
>simply slaps in format=flowed without following the specifications in the RFC,
>then blame that application. Again, do you know of any problem when both ends
>actually adhere to the specifications?
>
o By "the mail clients on both ends" do you mean only the software, or do
you mean to include the human beings? It is not practical to expect human
beings to conform all requirements of RFC 3676.
o Is there an available validator and data suite for format-flowed for both
sending and receiving ends? Human eyeball validation is impractical and
error-prone. (And quis custodiet ipsos custodes?)
o If such a validator were to exist, to whom would one report deviations?
What's the realistic likelihood of resolutions other than "WAD"?
o Does RFC 3676 guarantee round-trip integrity? Ed should be able to
copy-and-past his Rexx snippet and Don to extract it, byte-for-byte
identical to the original. Otherwise, the specification is a broken design.
Format=flowed had two (more?) design objectives:
o Support for comfortable viewing on hand-held fondleslabs.
o Support for word processors which reserve CRLF for paragraph separation.
These are pretty irrelevant to computer languages. Esmie's JCL was illegible
to Lizette; Ed's Rexx was illegible to Don.
If format=flowed imposes no requirement on the sending human being, it
SHOULD be possible to move all the flow-function from the sending MUA
to the receiving MUA and the receiving human being should be given a
{FLOWED|FIXED} button for viewing and extracting code respectively.
"Save as File" would suffice if that file could be guaranteed identical to
what the originator attached.
Many user agents do not allow disabling of "format=flowed".
-- 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: 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 both ends
>implement RFC 3676, then cut-and-paste works. If a brain dead application
>simply slaps in format=flowed without following the specifications in the RFC,
>then blame that application. Again, do you know of any problem when both ends
>actually adhere to the specifications?
>
o By "the mail clients on both ends" do you mean only the software, or do
you mean to include the human beings? It is not practical to expect human
beings to conform all requirements of RFC 3676.
o Is there an available validator and data suite for format-flowed for both
sending and receiving ends? Human eyeball validation is impractical and
error-prone. (And quis custodiet ipsos custodes?)
o If such a validator were to exist, to whom would one report deviations?
What's the realistic likelihood of resolutions other than "WAD"?
o Does RFC 3676 guarantee round-trip integrity? Ed should be able to
copy-and-past his Rexx snippet and Don to extract it, byte-for-byte
identical to the original. Otherwise, the specification is a broken design.
Format=flowed had two (more?) design objectives:
o Support for comfortable viewing on hand-held fondleslabs.
o Support for word processors which reserve CRLF for paragraph separation.
These are pretty irrelevant to computer languages. Esmie's JCL was illegible
to Lizette; Ed's Rexx was illegible to Don.
If format=flowed imposes no requirement on the sending human being, it
SHOULD be possible to move all the flow-function from the sending MUA
to the receiving MUA and the receiving human being should be given a
{FLOWED|FIXED} button for viewing and extracting code respectively.
"Save as File" would suffice if that file could be guaranteed identical to
what the originator attached.
Many user agents do not allow disabling of "format=flowed".
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Formatting (was: JCL ERROR : IGD01022I)
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 following the specifications in the RFC, then blame that application. Again, do you know of any problem when both ends actually adhere to the specifications? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Sunday, July 1, 2018 4: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 properly behaving mail client mangles >code properly formatted with format=flowed? > "properly formatted" is a big order. Before the infestation of format=flowed an author was able to copy-and-paste a code snippet into a message and the recipient could copy-and-paste and run it. Content-transfer-encoding: 8bit, now well supported removed one incentive to encode. RFC 822 mandated a 1000-character limit on line length, ample for coding. The feckless innovation of an 80-character limit impelled a new motive for encoding. In the message to which you're replying I experimented with UTF-8 text; long lines; 8bit. A surfeit of caution and timid adherence to Postel's rule has made things harder. Email shouldn't pretend to be a publishing tool. -- 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: 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 properly behaving mail client mangles >code properly formatted with format=flowed? > "properly formatted" is a big order. Before the infestation of format=flowed an author was able to copy-and-paste a code snippet into a message and the recipient could copy-and-paste and run it. Content-transfer-encoding: 8bit, now well supported removed one incentive to encode. RFC 822 mandated a 1000-character limit on line length, ample for coding. The feckless innovation of an 80-character limit impelled a new motive for encoding. In the message to which you're replying I experimented with UTF-8 text; long lines; 8bit. A surfeit of caution and timid adherence to Postel's rule has made things harder. Email shouldn't pretend to be a publishing tool. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Formatting (was: JCL ERROR : IGD01022I)
> 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 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: > 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 removed, JCL should render AOK. > In fact, Lizette may have a valid point, without stating a reason, which may lie in or around: https://secure-web.cisco.com/1IEKxYymw-faaABElSPcn7NMPT5uaebGx6eDwIDXu5PsVp6jf2POQOLccU0stXmIrC_e5QXhmf2bTFd5cfWOT3Q5Vy5k6A8YGX7iRpTUtMCr5jdc6kdHbdr9-qLTEGpukPPQdGCJH_o2_OA9KHSWkGyOrkaHvj2VfnpqC_DN4Stbjr5l-_kGj9uO77r1QcpqTeLWn7Lyk5EqBcuHkJh1lIyfA4z-cAy6bl6YbPfevsb09_Dsi6bKFzoe7xxFJBs7Q220aPnS1Ejv8_PauSeHZ1F4ypLo5wrbTgEmUfNsUv1Srf6K9OTG9orO6-3D6Tc03-8VrsRllyRfDIdYJw5TqhIJxbbGQAi8beDlVAK1PCrUEDR3KTMiXyYZNniyLS_i6aTbuMDKI_zARSBwxjrIq5jWxL5FEQI9EL4qBWJGoKyK8fvM2-IVYG-AgJxoannP9/https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc3676#section-4.1 However, the OP had merely: Content-Type: text/plain; charset=UTF-8 ... not "Format=Flowed", so RFC 3676 does not apply. I consider RFC 3676 an abomination, totally unsuitable for posting code samples. A MUA should provide an option to override it. As an experiment, I'll append 3 copies of a text/plain file with different Content-Transfer-Encoding: 8bit, quoted-printable, and base64, inline, but no Format=Flowed. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) +|+|+|+|+|+|+|+| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxx -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) +|+|+|+|+|+|+|+| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxx -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) +|+|+|+|+|+|+|+| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxx -- 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
Formatting (was: JCL ERROR : IGD01022I)
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. The problem is > trailing whitespace. With all trailing spaces removed, JCL should render AOK. > In fact, Lizette may have a valid point, without stating a reason, which may lie in or around: https://tools.ietf.org/html/rfc3676#section-4.1 However, the OP had merely: Content-Type: text/plain; charset=UTF-8 ... not "Format=Flowed", so RFC 3676 does not apply. I consider RFC 3676 an abomination, totally unsuitable for posting code samples. A MUA should provide an option to override it. As an experiment, I'll append 3 copies of a text/plain file with different Content-Transfer-Encoding: 8bit, quoted-printable, and base64, inline, but no Format=Flowed. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) +|+|+|+|+|+|+|+| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxx -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) +|+|+|+|+|+|+|+| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxx -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) +|+|+|+|+|+|+|+| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxx -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL ERROR : IGD01022I
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 removed, JCL should render AOK. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL ERROR : IGD01022I
@Jeremy Some shops build IEFBR14 like it is any other JCL including SYSPRINT SYSUT1, etc.. even though they are not needed. This is just something this shop does. IEFBR14 is still the same as the last billion years Lizette > -Original Message- > From: IBM Mainframe Discussion 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. > > /*//STEP1 > > EXEC PGM=IEFBR14 //SYSPRINT DD > > SYSOUT=* //SYSIN DD DUMMY > > //SYSUT1 DD DSN=PT5013.SMF... > > Leaving aside the JCL error, what on earth are you specifying > //SYSPRINT and //SYSUT1 for on an IEFBR14 step? > > Has something changed in the 20 years since I last did any of > this?IEFBR14 is not going to generate any SYSPRINT nor > need any utility/work files. > > -- > Jeremy Nicoll - my opinions are my own. > > -- > 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: JCL ERROR : IGD01022I
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 > //SYSUT1 DD DSN=PT5013.SMF... Leaving aside the JCL error, what on earth are you specifying //SYSPRINT and //SYSUT1 for on an IEFBR14 step? Has something changed in the 20 years since I last did any of this?IEFBR14 is not going to generate any SYSPRINT nor need any utility/work files. -- Jeremy Nicoll - my opinions are my own. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL ERROR : IGD01022I - PROBLEM SOLVED
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 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. /* //STEP1 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DSN=PT5013.SMF, // DCB=(RECFM=VBS,LRECL=32760,BLKSIZE=27998,DSORG=PS),// SPACE=(CYL,(2,1)),STORCLAS=NONSMS, // DISP=(,CATLG,DELETE),UNIT=3390,VOL=SER=ZE6632 I am not sure where the error is. The doc explanation (shown below) is not helpful: A specific volser specified in JCL, which is a non-library volume but a tape storage group is assigned OR the specified volume is a library volume but is not in the library at the time the job was run. System action Job failed with JCL err -- 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: JCL ERROR : IGD01022I
I cannot read the JCL listing. Please put at least 3 spaces when pasting JCL into email For example without spaces Line1 Line2 Line3 With spaces Line1 Line2 Line3 Second, looks like the ACS routines thing you may be using tape. I would go into ISMF and run a TEST on the data set 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 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 LIBRARYDTM1455I 2018.180 > 10:25:54 Job IEFBR14D failed, JCL Error Below is my JCL. > /*//STEP1EXEC > PGM=IEFBR14 //SYSPRINT DD SYSOUT=* >//SYSIN DD > DUMMY //SYSUT1 DD > DSN=PT5013.SMF, // DCB=(RECFM=VBS,LRE > CL=32760,BLKSIZE=27998,DSORG=PS),// SPACE=(CYL,(2,1)),STORCLAS=NONSMS > , // DISP=(,CATLG,DELETE),UNIT=3390,VOL=SER=ZE6632 > I am not sure where the error is. The doc explanation (shown below) is not > helpful: > A specific volser specified in JCL, which is a non-library volume but a tape > storage group is assigned OR the specified volume is a library volume but is > not in the library at the time the job was run. > > System action > > Job failed with JCL err > > > -- > 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
JCL ERROR : IGD01022I
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. /* //STEP1 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DSN=PT5013.SMF, // DCB=(RECFM=VBS,LRECL=32760,BLKSIZE=27998,DSORG=PS),// SPACE=(CYL,(2,1)),STORCLAS=NONSMS, // DISP=(,CATLG,DELETE),UNIT=3390,VOL=SER=ZE6632 I am not sure where the error is. The doc explanation (shown below) is not helpful: A specific volser specified in JCL, which is a non-library volume but a tape storage group is assigned OR the specified volume is a library volume but is not in the library at the time the job was run. System action Job failed with JCL err -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
