Re: Spool File export issue with iSeries Navigator

On 10/17/13 6:05 AM, Rich Dotson wrote:

We recently upgraded to V7.1. We have a user who uses iSeries
Navigator to download a spool file to her desktop. She then uses
Monarch to import that report into another system. The data in the
report starts in column 1. Now that we have upgraded to 7.1 the
Navigator "Export" function is adding 1 blank to the front of each
line on the report causing all of the data to shift to the right one
character causing an error by the Monarch import process. The spool
file is correct but the .txt file created is not. Has anyone else
seen this issue and how was it resolved? I've looked to see if there
is a PTF for this but haven't had any luck finding one.

Although not a resolution... knowing could be helpful.

A similar effect occurs for DBCS vs SBCS. As I recall, if a CPYSPLF is directed to a database file that was created with IGC(*YES), then there will be an extra blank character preceding each line irrespective the IGC setting of the spool file. In the ancient past, the effect may have been dependent upon the IGC setting of the spool file; i.e. no extra space character if the SPLF was IGC(*NO). When the target database file is IGC(*NO), then there is no extra blank character if the SPLF is also IGC(*NO), but the copy spool file request will fail with an error if the SPLF has IGC(*YES).