How to send GDG report as an attachment

gprerna · New User Joined: 21 Mar 2007 Posts: 38 Location: US

Hi,

I need to send a GDG through a job. I have coded a job, but i am getting the below error:

DATA SET UTILITY - GENERATE
WER171A CONCAT DS, LRECLS NE OR RECFMS DIFF
SYNCSORT COPY FEATURE CALLED - RC = 12

can someone guide me how to send a GDG as an attachment.

Thanks!!

dick scherrer · Posted: Thu May 03, 2007 2:35 am

Hello,

Please post your jcl and any related sysout information.

From the messages you posted, you are having problems in Syncsort. This "WER171A CONCAT DS, LRECLS NE OR RECFMS DIFF " says that your concatenated input data is not consistent (i.e. conflicting dcb info, recfm difference, etc).

I'm confused as to how Syncsort "sends" an attachment.

When you've posted your jcl/error info, we will be able to offer suggestions.

gprerna · New User Joined: 21 Mar 2007 Posts: 38 Location: US

hi,

Below is the code:

//SENDNOTE EXEC PGM=IEBGENER
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD SYSOUT=(B,SMTP)
//SYSUT1 DD *
HELO MVSHOST
MAIL FROM:<address@xxx.com>
RCPT TO:<address@xxx.com>
DATA
FROM:<address@xxx.com>
TO:<address@xxx.com>
SUBJECT: 'AGP REPORT FOR TODAY'
MIME-VERSION: 1.0
CONTENT-TYPE: MULTIPART/MIXED; BOUNDARY="BOUNDRY1"
--BOUNDRY1
CONTENT-TYPE: TEXT/PLAIN; CHARSET="US-ASCII"
CONTENT-TRANSFER-ENCODING: 7BIT
CONTENT-DISPOSITION:ATTACHMENT;FILENAME="ATTACH FILE.TXT"
CONTENT-TYPE: TEXT/HTML
// DD DISP=SHR,DSN=AXAX.AGP.REPORT.FINAL(0)
// DD *
--DELIMITER
.
QUIT
//*

and the error i am getting is:
********************************* TOP OF DATA ********
DATA SET UTILITY - GENERATE
WER171A CONCAT DS, LRECLS NE OR RECFMS DIFF
SYNCSORT COPY FEATURE CALLED - RC = 12
********************************

Please let me know in case you need more details.

Thanks!

dick scherrer · Posted: Thu May 03, 2007 2:52 am

Hello,

Your site dynamically invokes your sort product when it sees an IEBGENER that is performing a copy operation (the sort product typically copies faster than IEBGENER).

Please check the DCB info for this file DSN=AXAX.AGP.REPORT.FINAL(0).

After checking that DCB info, you'll probably want to copy your data from the DD * into a new file with the same DCB info. Once the new file is created, rerun using the new file instead of the DD *.

If that doesn't get past the error, we're here

gprerna · New User Joined: 21 Mar 2007 Posts: 38 Location: US

i copied the GDG version into a new file with the same attributes:

General Data Current Allocation
Management class . . : DEVLG Allocated cylinders : 1
Storage class . . . : DEV1000 Allocated extents . : 1
Volume serial . . . : 3WDL05
Device type . . . . : 3390
Data class . . . . . : ADDDSORG Current Utilization
Organization . . . : PS Used cylinders . . : 1
Record format . . . : FBA Used extents . . . : 1
Record length . . . : 133
Block size . . . . : 32718
1st extent cylinders: 1
Secondary cylinders : 50
Data set name type : SMS Compressible : NO

Creation date . . . : 2007/05/02 Referenced date . . : 2007/05/02
Expiration date . . : ***None***

it still doesnt work!!

But if i give DD DSN = AXAX.JCLLIB(MEM1)

it works!! Please let me know how i can do this with a GDG.

Thanks

dick scherrer · Posted: Thu May 03, 2007 3:28 am

Hello,

The initial problem was that the DD * data was not compatible with the "Record length . . . : 133 ". The DD * data is lrecl 80. Copying the GDG data to another file with the same DCB would not change the symptom.

The GDG is not part of the error. You need to copy the DD * data into a file that has the same dcb info as the GDG data.

Once both files have the same DCBs, the copy should work. Keep in mind that no changes should be needed for the current data in the GDG.

Having said that. . .

From one of my prior lives, i seem to recall sysout=b needed to be 80-byte records. Depending on how your system is set up, you may need to "go the other way" and copy your 133-byte data to an 80-byte record. This may not be desirable if your data goes beyond pos 80. We'll hope the first try works

gprerna · New User Joined: 21 Mar 2007 Posts: 38 Location: US

Do we have a limitation of sending a 80 byte (LRECL) file as an attachment. When i copied this file of 133 LRECL to a LRECL of 80 its working!!

dick scherrer · Posted: Thu May 03, 2007 4:58 am

Hello,