|
Post by Peter on Jun 12, 2015 0:25:06 GMT -5
SPF/Pro has a capability that would be good to see in SPF Lite.
In SPF/Pro the CREATE command can automatically translate between EBCDIC and ASCII and vice versa. This is done when the character set of the source and target files is different.
Say I have two profiles .PTF and .TXT where: PTF has RECFM=F LRECL=80 SOURCE=EBCDIC
TXT has RECFM=U LRECL=0 SOURCE=ANSI
If I copy lines from a .PTF file to create a .TXT file, then SPF/Pro will automatically translate those lines from EBCDIC to ASCII. Of course, it also adds or removes blanks as appropriate for the profiles.
In SPF/Pro, this automatic translation is done with the CREATE, CUT, PASTE and REPLACE edit commands.
|
|
|
Post by George on Jun 12, 2015 15:23:55 GMT -5
Peter: Robert: COPY is supposed to be copying in the data under control of the Profile of THAT file, not the file into which it is inserted. So there is definitely something going wrong right now. Let me chase this, it's simply a bug, not a design problem.
The request to have the output functions honor the filetype of the destination file type is probably worthy, but is not simply a small correction.
George
|
|
|
Post by Peter on Jun 14, 2015 19:59:30 GMT -5
Robert,George
I didn't think to try CUT and PASTE. I just tried them and found that I can achieve what I wanted using them instead.
But I'm still pleased to hear that CREATE and REPLACE will probably be fixed in a future release.
Thank you!
|
|