Format issues using XMITIP MSGDD

ssdjp1 · New User Joined: 22 Aug 2017 Posts: 6 Location: USA

I have one message that is not being formatted like I would really like to see.

In the XMITIP invocation I have
%XMITIP........ MSGDD MESG

//MESG DD *
Line1
Line2
Line3
Line4

When I get this message, it looks exactly like that.
Line1
Line2
Line3
Line4

The scenario I have where it formats incorrectly is being generated by a REXX program that is generating all the XMITIP pieces. The MESG dd is a temp file which is passed to the XMITIP step:

//MESG DD DISP=(NEW,PASS),LRECL=80,BLKSIZE=0,
// UNIT=3390,DSORG=PS,SPACE=(TRK,(1,1)),DSN=&&MESG

The REXX code :
mesg. = ""
mesg.1 = "STCVERIFY("jobid") Recap "date() time()
mesg.2 = "Recap of Started TASKS not active:"
mesg.3 = error_jobs
mesg.0 = 3
"execio * diskw MESG (stem mesg. finis"

The resulting email is not formatted correctly:
STCVERIFY(STC06753) Recap 23 Oct 2017 10:51:25 Recap of Started TASKS not active:
DJPJ12 TSO

I want it to look like:
STCVERIFY(STC06753) Recap 23 Oct 2017 10:51:25
Recap of Started TASKS not active:
DJPJ12 TSO

Suggestions?

Nic Clouston · Posted: Mon Oct 23, 2017 9:30 pm

Please use the code tags for code and data.

Where is this being viewed - z/os or l/u/w?
If the latter then have you tried inserting the appropriate end of line char[s] after mesg.1 (although thiseems to be ok between mesg.2 and 3,

Style-wise you should not write * lines but mesg.0 lines. One day you might get caught short and not all lines get written.

ssdjp1 · New User Joined: 22 Aug 2017 Posts: 6 Location: USA

Thanks Nic. "Where is this being viewed"? Do you mean in what email client (Outlook). we are running z/OS 1.13

daveporcelan · Posted: Mon Oct 23, 2017 10:39 pm

Instead of this:

Marso · Posted: Tue Oct 24, 2017 2:34 pm

Which other options do you have in your XMITIP command ?
If there is any HTML, then you should do:

ssdjp1 · New User Joined: 22 Aug 2017 Posts: 6 Location: USA

Thanks for the help. I branched off trying Nic's idea of an EBCDIC CRLF to see if that would make it separate the message. I added '15'x to the end of the mesg.1 and that cured the issue. Weird - never seen this before. In over 20years of using XMITIP, this was a first. Thanks for the help and suggestions.