That’s a strange response to people copying the code. The only code that could be copied should be from CL commands that were logged — and that can be eliminated easily by compiling the CL as LOG(*NO).

But error messages should actually need coding to remove them from the joblog or to suppress them from appearing. Errors are separate from any logging of CL code. Suppression or removal of error messages doesn’t seem to make much sense.

And if CVTPFXLS isn’t running much CL but RPG or other HLL instead, then suppression of errors makes even less sense (to me).

Still, it’s useful to know that logging may be unavailable.

Tom

<quote>
The version you downloaded does not show logs because I removed the logging within the program. I found a few people in the industry that tried to copy my codes and published it with their name. Since this is a free-ware I gave out to the community, people have asked that I place logging back – I regret to acknowledge, not right now.

</quote>

I use this command for down and dirty conversions. If I need more control over how rows and columns are formatted, I use the POI API’s.

If there is no joblog, how can you see the message? The message itself is almost certainly in the joblog.

When you see that message, move your cursor to it and press the <F1> key. When the ‘Additional Message Information’ screen displays, press the <F10=Display messages in job log> key. Scroll backwards to see if there are other messages that indicate any kind of failure.

If no messages appear, then change your job to log all messages.

CHGJOB LOG(4 00 *SECLVL)

Then run the CVTPFXLS command again the same way. Then look into the joblog.

Let us know what you find.

Tom