| View previous topic :: View next topic |
| Author |
Message |
amargulies Beginner
Joined: 10 Jan 2007 Posts: 123 Topics: 0
|
Posted: Tue Oct 28, 2008 10:45 am Post subject: |
|
|
Based on the latest listings, the WER275A message appears to be caused by a coding error (the /* did not begin in column 1). _________________ Alissa Margulies
SyncSort Mainframe Product Services
201-930-8260
zos_tech@syncsort.com |
|
| Back to top |
|
 |
Dibakar Advanced

Joined: 02 Dec 2002 Posts: 702 Topics: 64 Location: USA
|
Posted: Wed Oct 29, 2008 10:36 pm Post subject: |
|
|
chandra,
I assume that you didn't try the rexx solution as I notice there is a small bug there.
Anyway, for learning purpose, I tried a SAS solution. Since you had asked about SAS books earlier so I am assuming you have access to SAS.
You can try this untested SAS code (this is just the corrected version of the REXX code)
| Code: | //STEP010 EXEC SAS...
//SYSPRINT DD SYSOUT=*
//PREMERGE DD ...
//MERGED DD ...
//SYSIN DD *
data _null_;
infile premerge end=done;
file merged;
input newline $ 1-80;
do while (not done);
input field1 $ 1-39 field2 $ 40 field3 $ 41-80;
if (field2 = '1') then do;
put @1 newline $1;
newline = cat(field1,field2,field3);
end;
else newline = cat(newline,field3);
end;
put @1 newline $1;
//* |
Diba |
|
| Back to top |
|
 |
chandra Beginner
Joined: 26 Sep 2003 Posts: 130 Topics: 36
|
Posted: Fri Oct 31, 2008 3:57 pm Post subject: |
|
|
Hi Diba,
Actualy I ran your code and fixed the defect but I forgot to mention in my reply.... anyway thanks for your response..
Alisa,
You are correct there wsa an codeing error (/* not begin in column 1). Thank you very much for your help. _________________ Regards,
Chandra |
|
| Back to top |
|
 |
|
|
|