Can CMOD handle 'Channel Oriented Carriage Control'.

[pankaj.puranik]

Hi

I have a report that uses an overlay.
For data to properly fit on the form, the input file has carriage control characters.
After passing the report through the indexer, the output file is not having proper line spacing.
This makes me feel that CMOD is not able to interpret this type of CC.

The CC in the files are : 1, 3, 4, etc.

Does anyone have experience with this type of CC.

CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
MCF2REF=CPCS

[pankaj.puranik]

Does anyone have a solution/suggestion to this issue?
We are using EBCDIC Line data.

[Greg Ira]

We don't use EBCDIC Channel Oriented CC so I can't speak as to whether CMOD can handle that.  If it doesn't maybe you could use an input exit to transform the EBCDIC CC to Machine CC?  I know CMOD can handle that.

[Greg Ira]

In addition, according to the manual it does look like CMOD should handle your Channel Oriented CCs.  Did you double check the LRECL?

[pankaj.puranik]

Thanks Greg.
The Rec Length is correctly mentioned.

I have one more question.
After CMOD process the IBMLINE data or any other data, does it still have the carriage control byte or it inserts the spaces after interpreting the CC and then store the file?

So when I retrieve a file stored in CMOD in native format, would it have CC bytes or actual spaces?

[Greg Ira]

It would still have the CC bytes, it doesn't overwrite them

[ewirtz]

Hello Pankaj,

only some of the possible ansi control characters have a well defined behaviour: '+', '0', ' ' and '1'. The other are configured individually. I don't know how CMOD does treat such ansi characters. But I think a general solution for such characters is not possible.  So maybe you have to create an index exit to provide only 'well known ansi characters' or provide a preview exit that corrects such problematic characters.

Regards

Egon