Re: Is this a CCSID thing? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hello Thomas,

Am 16.06.2023 um 21:39 schrieb tgarvey@xxxxxxxxxx:

We had the client (in Latin America) copy the image file from their IFS to a thumb drive, and send us the tumb drive.

How exactly did they do this copy process? FTP? Probably used mode ASCII (which is WRONG for binary files like any image file)?

CPDBC0C Image file not valid for image catalogs of type *TAP

The image file specified on the FROMFILE parameter is not valid for an image catalog of type *TAP

When I look at the CCSID of the original Image file on the client's server, it has 819 (Latin-1) as the CCSID.

When it appears on our IFS it has CCSID 1252 (Latin-1 for Windows).

That should only matter if the characters being used for the images themselves are outside the usual OS/400 naming restrictions.

But the error message is that the *image file* is not valid for a *TAP catalog. There's no mentioning about the catalog itself (which can be rebuilt moderately easily anytime, anyway).

I bet they used FTP for transfer and this garbled the contents of the image files so it can't be recognized as an image file by IBM i anymore.

Also, see Peter Dow's answer.

:wq! PoC

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.