× 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 

We move on customer from V5R2 to V5R3. 

I do recognize that now I can't print any printout if they make
references as external *PRTF to DB fields, defined "O", as DBCS ready
database.

On V5R2, no problems appear.  
 
The writer answers that the *PRTF is not supported, and ask by message
to put in hold or cancel the writer, is producing as: 

Message ID . . . . . . :   CPA3303

 Date sent  . . . . . . :   09/08/06      Time sent  . . . . . .
:12:45:34

 Message . . . . :   Attributes of file SIN641O not supported for device
KATWHPP1. (C G H)

Cause . . . . . :   Writer KATWHPP1 found attributes of file SIN641O
number 1 job 848486/SAVV8/QPADEV0002 created on system S44D1363 on
09/08/06 12:44:43 on output queue KATWHPP1 in library QUSRSYS that are
not supported for device KATWHPP1. The error code, or codes, are  5.
The error codes and
their meaning are as follows:

     1 - Page size of file not supported on device.

     2 - Device type of file not supported on device.

     3 - Lines per inch (LPI) of file not supported on device.

     4 - Special device requirements of file not supported on device.

     5 - UCS-2 data or IGC data (IGCDTA), IGC character rotation
(IGCCHRRTT),IGC characters per inch (IGCCPI), or IGC shift-out and
shift-in characters (IGCSOSI) not supported on device.


This can be answer by "G", and for 132 layout but if you are on 198 (15
cpi), comes out on 132, double lines cut out. 

I change & try all the option that CRTPRTF offers related to IGCDTA, but
it does not works. 

Now, I can see 2 solution: 

1)     Wipe all the reffld on PRTF, and put the dimension directly 
2)     Go to 132  

The 2 is not applicable, for the big amount of info on one line
The 1, can stands, big rework, but the customer will remain unsatisfied.
Anyhow problems. 

Have you ever seen such problem?

Are you experienced with solution on this, as solution / workaround?  

Any suggestion is appreciate.

Thanks
Regards


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.