Re: Problem with XMITIP, TXT attachment and ZVM / NJE
On Fri, 28 Sep 2018 02:45:04 -0500, Jean-Loup PIETIN wrote: >Hi sorry for the delay of response... > >it was converted like when you download text file from ZOS in FTP in mode >BINARY, not in ASCII. > >so the JES2 job transmit to RSCS and SMTP in ZVM contain the directive in >clear text and the attachement in binary > >Jean-Loup PIETIN > Please refresh our memories; exactlly what command and options did you use? Can you attach the first few lines of the "attachement in binary"? I'll still suggest bypassing XMITIP and using instead: TRANSMIT node.user_id DATASET(dsname) MEMBERS(member) SEQUENTIAL -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
Hi sorry for the delay of response... it was converted like when you download text file from ZOS in FTP in mode BINARY, not in ASCII. so the JES2 job transmit to RSCS and SMTP in ZVM contain the directive in clear text and the attachement in binary Jean-Loup PIETIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE
On Fri, 21 Sep 2018 17:58:44 -0500, Mike Schwab wrote: >I'm wondering if they TERSEd the file? > The OP was asking how to create an attachment from a PDS member, not how to deal with an existing one. And the problem arose with LRECL>204. But: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieav100/allocon.htm ... says: The data set compressed by AMATERSE (produced by PACK or SPACK) must be of fixed or fixed-blocked record format with a record length (LRECL) of 1024 ... ... which violates LRECL<=204. >On Fri, Sep 21, 2018 at 11:49 AM Dyck, Lionel B. (RavenTek) wrote: >> >> My understanding is that this is an NJE issue. The user is using XMITIP to >> generate an e-mail in SMTP format, placing the data in the JES Spool routed >> to z/VM where the SMTP server is that then sends the e-mail somewhere. I >> suspect it has something to do with record size limitations on the NJE data. >> XMITIP will let the user know if the data exceeds the SMTP LRECL limit >> already. >> >> I suspect they are JES2 but could be using JES3 - in either case does anyone >> know of any LRECL restrictions on data flowing across NJE as that would help >> the OP. In the original ply: ... We use XMITIP to send mail from Z/Os 2.1 via a NJE node to Z/VM 6.4 ... It sounds as if z/VM (CMS? Probably not Linux) is the ultimate destination, not an intermediate MTA. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE
I'm wondering if they TERSEd the file? On Fri, Sep 21, 2018 at 11:49 AM Dyck, Lionel B. (RavenTek) <01d7f21a6167-dmarc-requ...@listserv.ua.edu> wrote: > > My understanding is that this is an NJE issue. The user is using XMITIP to > generate an e-mail in SMTP format, placing the data in the JES Spool routed > to z/VM where the SMTP server is that then sends the e-mail somewhere. I > suspect it has something to do with record size limitations on the NJE data. > XMITIP will let the user know if the data exceeds the SMTP LRECL limit > already. > > I suspect they are JES2 but could be using JES3 - in either case does anyone > know of any LRECL restrictions on data flowing across NJE as that would help > the OP. > > -- > 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 Paul Gilmartin > Sent: Friday, September 21, 2018 8:31 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE > > On Fri, 21 Sep 2018 04:00:45 -0500, Jean-Loup PIETIN wrote: > > >Hi > > > >i use FORMAT TXT/filename.TXT > > > >if i use FORMAT XMIT/filename.TXT, the content is converted in binary and is > >not in good format when i open the attachment... > > > Is this an ASCII-EBCDIC problem? Shouldn't be since both z/OS and z/VM are > EBCDIC. > > -- 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 -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
On Fri, 21 Sep 2018 21:30:26 +, Seymour J Metz wrote: >Searching for FORMAT XMIT gives only three hits. > OK. Once I quote the search target the right way. > The Guide says, If the input is not in TSO Transmit format then XMITIP will use TSO Transmit to put it into XMIT format. Does XMITIP of a PDS member invoke TRANSMIT with the SEQ option? (The Guide doesn't say.) Can the user control this? Lacking SEQ, TRANSMIT unloads the member with IEBCOPY and the resulting PDSU format is alien to CMS. The user might need to do a TRANSMIT SEQ OUTDATASET() to avoid this. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
Searching for FORMAT XMIT gives only three hits. -- 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: Friday, September 21, 2018 4:19 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Problem with XMITIP, TXT attachment and ZVM / NJE On Fri, 21 Sep 2018 19:16:31 +, Seymour J Metz wrote: >Yes. FORMAT XMIT. > Searching for XMIT in http://secure-web.cisco.com/1jHHKiAnuF-aGjRgXnDo2kGLogMUPJclpPRY0MGxPwVjHMn1zIVrVDscPT6uqbahHiv56FddWNIySQ23znSGSV36HkJNI3Q2AwsGGqrZEeH_uRj-SHksMo-BZbnPxbt0qlCiSIMaV-3kQ-3kB6C8iqsh_p6nGuHcsnyWPS8z14Ba6GIFOX3vNQJgXh9QFHKC5cQpPnAXLwdTTK1AbfLKj-CDn4egtrVZGYWnIeqTquJEXx0n-w-1rm5rl5id9eevzDq5cOf7DQzT5-jlHgq7vqhbcbQDIOykG17GuQbtNsSzlrlUohoZX50sC4tvtYcS90ePb_gzPcV1zVuXaTM3AUhPEnLvchsqPmvRVLwL9-8HbXkJZ_vPfKOCEhVgQW7Ugm5iPLZGCwq_aUdjbtsUPmuxdfc09sdhbQOa2j3XHrtKuZTrGsI0wQ8EbSj9IlUPj/http%3A%2F%2Fwww.lbdsoftware.com%2FXMITIP-Guide.pdf gives a terrible S/N ratio. It says XMIT will be transmitted as a binary attachment. May I assume Content-Transfer-Encoding: base64? What Content-Type? Then it might be restored on CMS with (untested, a guess): PIPE < attachment | (discard headers and footers) | 64DECODE | FBLOCK 80 | NETDATA | PAD 1 | > fn ft TXT -- 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: Problem with XMITIP, TXT attachment and ZVM / NJE
On Fri, 21 Sep 2018 19:16:31 +, Seymour J Metz wrote: >Yes. FORMAT XMIT. > Searching for XMIT in http://www.lbdsoftware.com/XMITIP-Guide.pdf gives a terrible S/N ratio. It says XMIT will be transmitted as a binary attachment. May I assume Content-Transfer-Encoding: base64? What Content-Type? Then it might be restored on CMS with (untested, a guess): PIPE < attachment | (discard headers and footers) | 64DECODE | FBLOCK 80 | NETDATA | PAD 1 | > fn ft TXT -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
What do you mean by "converted to binary"? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Jean-Loup PIETIN Sent: Friday, September 21, 2018 5:00 AM To: IBM-MAIN@listserv.ua.edu Subject: Re: Problem with XMITIP, TXT attachment and ZVM / NJE Hi i use FORMAT TXT/filename.TXT if i use FORMAT XMIT/filename.TXT, the content is converted in binary and is not in good format when i open the attachment... -- 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: Problem with XMITIP, TXT attachment and ZVM / NJE
Yes. FORMAT XMIT. -- 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: Friday, September 21, 2018 2:45 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE On Fri, 21 Sep 2018 16:48:29 +, Dyck, Lionel B. (RavenTek) wrote: >My understanding is that this is an NJE issue. The user is using XMITIP to >generate an e-mail in SMTP format, placing the data in the JES Spool routed to >z/VM where the SMTP server is that then sends the e-mail somewhere. I suspect >it has something to do with record size limitations on the NJE data. XMITIP >will let the user know if the data exceeds the SMTP LRECL limit already. > >I suscect they are JES2 but could be using JES3 - in either case does anyone >know of any LRECL restrictions on data flowing across NJE as that would help >the OP. On Thu, 20 Sep 2018 07:50:51 -0500, Jean-Loup PIETIN wrote: > >But we have a problem with txt file attachment.. when we send a file with line >length > 204 characters … the mail was doesn’t sent… > >We have open a PMR with IBM but no solution found… > >In cause, the mail object was send in VAFP print file and the SMTP partition >on Z/VM don’t support the VAFP print file…. > (VAFP = Virtual Advanced Function Printer?) I believe that some z/VM components, but not all, support VAFP https://secure-web.cisco.com/1BDXQ0tWtpDsTtYntFLePRB3Hm6wIW9SepcYi9WBJbTerr-ErctLIovy2QLItN86wkFL04jGAsQ7FuS6DAMp39-X5TVmEdy7Eb8FqGyhyx1oRj8wfdD2NYO9jNk02KfHxQEITgn4-eVw6v4QcSq41e3Ryj2vXK8zG_fit0-jaCKa3hIaT-5nQJbAmdPChPKg8K2M6aSJrrOj_RjY4C4uuMI-tFFSp7v8t0g3lQKl3Y91JtxRS9TFUOyixQvD6FSP4iatyBu2rCJfcqI04aCrOgw0AoWupOnBATcYo5CsKn7zyh47siaFeboe0FrP-9mgrgShrOfJLEdKHonHZB9Cr0by0Yy9Vt_S10EH-w6oH_HbfBWmJVhZbCsvbO82kNsPLXFPA_ZJ2cXWXYZZYUL3AZMUqfw_i4K_oICQ2GGQ7kVOkzsd-GOO10WyPVxEsoS2r/https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSB27U_6.4.0%2Fcom.ibm.zvm.v640.hcpb7%2Fdefspdev.htm z/VM 6.4.0> Operation and Use> z/VM: CP Commands and Utilities Reference> CP Commands ...references "CP DEFINE VAFP ..." with lotsa restrictions in the Usage Notes. I once tried unsuccessfully to use VAFP to send an email message from CMS with "PIPE URO ..." The obstacle may have been RSCS. Does XMITIP support NETDATA (TSO TRANSMIT) format? NETDATA is well supported by RSCS and by CMS PIPE NETDATA. -- 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: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE
On Fri, 21 Sep 2018 16:48:29 +, Dyck, Lionel B. (RavenTek) wrote: >My understanding is that this is an NJE issue. The user is using XMITIP to >generate an e-mail in SMTP format, placing the data in the JES Spool routed to >z/VM where the SMTP server is that then sends the e-mail somewhere. I suspect >it has something to do with record size limitations on the NJE data. XMITIP >will let the user know if the data exceeds the SMTP LRECL limit already. > >I suscect they are JES2 but could be using JES3 - in either case does anyone >know of any LRECL restrictions on data flowing across NJE as that would help >the OP. On Thu, 20 Sep 2018 07:50:51 -0500, Jean-Loup PIETIN wrote: > >But we have a problem with txt file attachment.. when we send a file with line >length > 204 characters … the mail was doesn’t sent… > >We have open a PMR with IBM but no solution found… > >In cause, the mail object was send in VAFP print file and the SMTP partition >on Z/VM don’t support the VAFP print file…. > (VAFP = Virtual Advanced Function Printer?) I believe that some z/VM components, but not all, support VAFP https://www.ibm.com/support/knowledgecenter/en/SSB27U_6.4.0/com.ibm.zvm.v640.hcpb7/defspdev.htm z/VM 6.4.0> Operation and Use> z/VM: CP Commands and Utilities Reference> CP Commands ...references "CP DEFINE VAFP ..." with lotsa restrictions in the Usage Notes. I once tried unsuccessfully to use VAFP to send an email message from CMS with "PIPE URO ..." The obstacle may have been RSCS. Does XMITIP support NETDATA (TSO TRANSMIT) format? NETDATA is well supported by RSCS and by CMS PIPE NETDATA. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE
The specification for NJE are found in SA22-7539. Tony Thigpen Dyck, Lionel B. (RavenTek) wrote on 09/21/2018 12:48 PM: My understanding is that this is an NJE issue. The user is using XMITIP to generate an e-mail in SMTP format, placing the data in the JES Spool routed to z/VM where the SMTP server is that then sends the e-mail somewhere. I suspect it has something to do with record size limitations on the NJE data. XMITIP will let the user know if the data exceeds the SMTP LRECL limit already. I suspect they are JES2 but could be using JES3 - in either case does anyone know of any LRECL restrictions on data flowing across NJE as that would help the OP. -- 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 Paul Gilmartin Sent: Friday, September 21, 2018 8:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE On Fri, 21 Sep 2018 04:00:45 -0500, Jean-Loup PIETIN wrote: Hi i use FORMAT TXT/filename.TXT if i use FORMAT XMIT/filename.TXT, the content is converted in binary and is not in good format when i open the attachment... Is this an ASCII-EBCDIC problem? Shouldn't be since both z/OS and z/VM are EBCDIC. -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE
My understanding is that this is an NJE issue. The user is using XMITIP to generate an e-mail in SMTP format, placing the data in the JES Spool routed to z/VM where the SMTP server is that then sends the e-mail somewhere. I suspect it has something to do with record size limitations on the NJE data. XMITIP will let the user know if the data exceeds the SMTP LRECL limit already. I suspect they are JES2 but could be using JES3 - in either case does anyone know of any LRECL restrictions on data flowing across NJE as that would help the OP. -- 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 Paul Gilmartin Sent: Friday, September 21, 2018 8:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Problem with XMITIP, TXT attachment and ZVM / NJE On Fri, 21 Sep 2018 04:00:45 -0500, Jean-Loup PIETIN wrote: >Hi > >i use FORMAT TXT/filename.TXT > >if i use FORMAT XMIT/filename.TXT, the content is converted in binary and is >not in good format when i open the attachment... > Is this an ASCII-EBCDIC problem? Shouldn't be since both z/OS and z/VM are EBCDIC. -- 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: Problem with XMITIP, TXT attachment and ZVM / NJE
On Fri, 21 Sep 2018 04:00:45 -0500, Jean-Loup PIETIN wrote: >Hi > >i use FORMAT TXT/filename.TXT > >if i use FORMAT XMIT/filename.TXT, the content is converted in binary and is >not in good format when i open the attachment... > Is this an ASCII-EBCDIC problem? Shouldn't be since both z/OS and z/VM are EBCDIC. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
Thank's Tony I wiil see if it's possible to evolve the XMITIP program to convert TXT file in BASE64 or see if i found a solution to do this myself... Jean-Loup PIETIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
Hi i use FORMAT TXT/filename.TXT if i use FORMAT XMIT/filename.TXT, the content is converted in binary and is not in good format when i open the attachment... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
What was the exact command you used? FORMAT XMIT should have worked. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Jean-Loup PIETIN Sent: Thursday, September 20, 2018 8:50 AM To: IBM-MAIN@listserv.ua.edu Subject: Problem with XMITIP, TXT attachment and ZVM / NJE Hi I’m Jean-Loup PIETIN from FRANCE and I work like System Analyst on ZOS 2.1 I wrote you because we encounter a problem with your XMITIP program in version 18.07 and the author of this program (Lionel B Dyck) advise me to search in this forum. This is the message that i wrote to Lionel : We use XMITIP to send mail from Z/Os 2.1 via a NJE node to Z/VM 6.4… But we have a problem with txt file attachment.. when we send a file with line length > 204 characters … the mail was doesn’t sent… We have open a PMR with IBM but no solution found… In cause, the mail object was send in VAFP print file and the SMTP partition on Z/VM don’t support the VAFP print file…. The solution for the moment is to send the TXT attachment in ZIP format but when we use the ZIP format, we use CPU consumption on Z/Os and the goal of our migration of XMITIP via NJE is to decrease the CPU consumption. That’s why we wrote a program in JAVA to ZIP PDS file for use the ZIIP processor before send mail with XMITIP…but if it’s possible to keep the format TXT when we use the VIANJE option with Z/VM, it will be good. I don’t know if it’s possible to encode in BASE64 the txt file when we transmit the mail but it will be a solution like the PDF or BIN format… Thanks a lot for reading me and I hope to find the best solution. And the response of Lionel was : I would like to help but I am not in a site with NJE – however all XMITIP does when used in the NJE mode is to generate SMTP data in the JES SPOOL for routing to an SMTP started task at another JES node. I am not aware of LRECL limitations (mostly I don’t remember if there are). IBM should be able to provide insight into the NJE LRECL limitations of both JES and z/VM for you. You can ask your question on the IBM-Main Listserv as someone there is very likely to be able to give you some advice as well. Let me know how you resolve this – I’m sorry that I don’t have a better answer for you. Lionel If anyone know how i can send a mail with txt attachement line length >204 without ZIp it, i'll take it Best Regard Jean-Loup PIETIN -- 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: Problem with XMITIP, TXT attachment and ZVM / NJE
I'd create the file in XMIT Outdsn format and then send that dataset via XMITIP to VM Jerry Whitteridge Delivery Manager / Mainframe Architect GTS - Safeway Account 602 527 4871 Mobile jerry.whitteri...@ibm.com IBM Services IBM Mainframe Discussion List wrote on 09/20/2018 05:50:51 AM: > From: Jean-Loup PIETIN > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 09/20/2018 06:02 AM > Subject: Problem with XMITIP, TXT attachment and ZVM / NJE > Sent by: IBM Mainframe Discussion List > > Hi > > I’m Jean-Loup PIETIN from FRANCE and I work like System Analyst on ZOS 2.1 > > I wrote you because we encounter a problem with your XMITIP program > in version 18.07 and the author of this program (Lionel B Dyck) > advise me to search in this forum. > > This is the message that i wrote to Lionel : > > We use XMITIP to send mail from Z/Os 2.1 via a NJE node to Z/VM 6.4… > > But we have a problem with txt file attachment.. when we send a file > with line length > 204 characters … the mail was doesn’t sent… > > We have open a PMR with IBM but no solution found… > > In cause, the mail object was send in VAFP print file and the SMTP > partition on Z/VM don’t support the VAFP print file…. > > The solution for the moment is to send the TXT attachment in ZIP > format but when we use the ZIP format, we use CPU consumption on Z/ > Os and the goal of our migration of XMITIP via NJE is to decrease > the CPU consumption. > > That’s why we wrote a program in JAVA to ZIP PDS file for use the > ZIIP processor before send mail with XMITIP…but if it’s possible to > keep the format TXT when we use the VIANJE option with Z/VM, it will be good. > > I don’t know if it’s possible to encode in BASE64 the txt file when > we transmit the mail but it will be a solution like the PDF or BIN format… > > Thanks a lot for reading me and I hope to find the best solution. > > And the response of Lionel was : > > I would like to help but I am not in a site with NJE – however all > XMITIP does when used in the NJE mode is to generate SMTP data in > the JES SPOOL for routing to an SMTP started task at another JES > node. I am not aware of LRECL limitations (mostly I don’t remember > if there are). IBM should be able to provide insight into the NJE > LRECL limitations of both JES and z/VM for you. > > You can ask your question on the IBM-Main Listserv as someone there > is very likely to be able to give you some advice as well. > > Let me know how you resolve this – I’m sorry that I don’t have a > better answer for you. > > Lionel > > > If anyone know how i can send a mail with txt attachement line > length >204 without ZIp it, i'll take it > > Best Regard > > Jean-Loup PIETIN > > -- > 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: Problem with XMITIP, TXT attachment and ZVM / NJE
> I don’t know if it’s possible to encode in BASE64 the txt file when > we transmit the mail but it will be a solution like the PDF or BIN > format… PDF and BIN files are sent as BASE64. BASE64 encoding of TXT files is normal in the email world. That is your best approach. Tony Thigpen Jean-Loup PIETIN wrote on 09/20/2018 08:50 AM: Hi I’m Jean-Loup PIETIN from FRANCE and I work like System Analyst on ZOS 2.1 I wrote you because we encounter a problem with your XMITIP program in version 18.07 and the author of this program (Lionel B Dyck) advise me to search in this forum. This is the message that i wrote to Lionel : We use XMITIP to send mail from Z/Os 2.1 via a NJE node to Z/VM 6.4… But we have a problem with txt file attachment.. when we send a file with line length > 204 characters … the mail was doesn’t sent… We have open a PMR with IBM but no solution found… In cause, the mail object was send in VAFP print file and the SMTP partition on Z/VM don’t support the VAFP print file…. The solution for the moment is to send the TXT attachment in ZIP format but when we use the ZIP format, we use CPU consumption on Z/Os and the goal of our migration of XMITIP via NJE is to decrease the CPU consumption. That’s why we wrote a program in JAVA to ZIP PDS file for use the ZIIP processor before send mail with XMITIP…but if it’s possible to keep the format TXT when we use the VIANJE option with Z/VM, it will be good. I don’t know if it’s possible to encode in BASE64 the txt file when we transmit the mail but it will be a solution like the PDF or BIN format… Thanks a lot for reading me and I hope to find the best solution. And the response of Lionel was : I would like to help but I am not in a site with NJE – however all XMITIP does when used in the NJE mode is to generate SMTP data in the JES SPOOL for routing to an SMTP started task at another JES node. I am not aware of LRECL limitations (mostly I don’t remember if there are). IBM should be able to provide insight into the NJE LRECL limitations of both JES and z/VM for you. You can ask your question on the IBM-Main Listserv as someone there is very likely to be able to give you some advice as well. Let me know how you resolve this – I’m sorry that I don’t have a better answer for you. Lionel If anyone know how i can send a mail with txt attachement line length >204 without ZIp it, i'll take it Best Regard Jean-Loup PIETIN -- 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: Problem with XMITIP, TXT attachment and ZVM / NJE
Yes. Maximum line length that JES2/3 supports. On Thu, Sep 20, 2018 at 8:56 AM Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Thu, 20 Sep 2018 07:50:51 -0500, Jean-Loup PIETIN wrote: > > > >I’m Jean-Loup PIETIN from FRANCE and I work like System Analyst on ZOS 2.1 > > > >I wrote you because we encounter a problem with your XMITIP program in > >version 18.07 and the author of this program (Lionel B Dyck) advise me to > >search in this forum. > > > >This is the message that i wrote to Lionel : > > > >We use XMITIP to send mail from Z/Os 2.1 via a NJE node to Z/VM 6.4… > > > >But we have a problem with txt file attachment.. when we send a file with > >line length > 204 characters … the mail was doesn’t sent… > > > Quel dommage. A consequence of making everything look like a printer. > > NETDATA format is generated by TSO TRANSMIT and CMS SENDFILE and understood > by TSO and CMS RECEIVE and well accepted by RSCS. Might this provide a > solution? > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Problem with XMITIP, TXT attachment and ZVM / NJE
On Thu, 20 Sep 2018 07:50:51 -0500, Jean-Loup PIETIN wrote: > >I’m Jean-Loup PIETIN from FRANCE and I work like System Analyst on ZOS 2.1 > >I wrote you because we encounter a problem with your XMITIP program in version >18.07 and the author of this program (Lionel B Dyck) advise me to search in >this forum. > >This is the message that i wrote to Lionel : > >We use XMITIP to send mail from Z/Os 2.1 via a NJE node to Z/VM 6.4… > >But we have a problem with txt file attachment.. when we send a file with line >length > 204 characters … the mail was doesn’t sent… > Quel dommage. A consequence of making everything look like a printer. NETDATA format is generated by TSO TRANSMIT and CMS SENDFILE and understood by TSO and CMS RECEIVE and well accepted by RSCS. Might this provide a solution? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Problem with XMITIP, TXT attachment and ZVM / NJE
Hi I’m Jean-Loup PIETIN from FRANCE and I work like System Analyst on ZOS 2.1 I wrote you because we encounter a problem with your XMITIP program in version 18.07 and the author of this program (Lionel B Dyck) advise me to search in this forum. This is the message that i wrote to Lionel : We use XMITIP to send mail from Z/Os 2.1 via a NJE node to Z/VM 6.4… But we have a problem with txt file attachment.. when we send a file with line length > 204 characters … the mail was doesn’t sent… We have open a PMR with IBM but no solution found… In cause, the mail object was send in VAFP print file and the SMTP partition on Z/VM don’t support the VAFP print file…. The solution for the moment is to send the TXT attachment in ZIP format but when we use the ZIP format, we use CPU consumption on Z/Os and the goal of our migration of XMITIP via NJE is to decrease the CPU consumption. That’s why we wrote a program in JAVA to ZIP PDS file for use the ZIIP processor before send mail with XMITIP…but if it’s possible to keep the format TXT when we use the VIANJE option with Z/VM, it will be good. I don’t know if it’s possible to encode in BASE64 the txt file when we transmit the mail but it will be a solution like the PDF or BIN format… Thanks a lot for reading me and I hope to find the best solution. And the response of Lionel was : I would like to help but I am not in a site with NJE – however all XMITIP does when used in the NJE mode is to generate SMTP data in the JES SPOOL for routing to an SMTP started task at another JES node. I am not aware of LRECL limitations (mostly I don’t remember if there are). IBM should be able to provide insight into the NJE LRECL limitations of both JES and z/VM for you. You can ask your question on the IBM-Main Listserv as someone there is very likely to be able to give you some advice as well. Let me know how you resolve this – I’m sorry that I don’t have a better answer for you. Lionel If anyone know how i can send a mail with txt attachement line length >204 without ZIp it, i'll take it Best Regard Jean-Loup PIETIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
