× 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.



Bradley,

The problem is in the CPYSPLF command using the *TOSTMF option with the
*PDF option, not in MAILR. MAILR does not create the object that is to
be attached to the email. I became aware of the problem using that
program.

Does anyone have any idea of how to control the CCSID that CPYSPLF uses
when create a PDF in the IFS?

Thanks,

Marvin

----------------------------------------------------------------------

message: 1
date: Wed, 24 Aug 2011 15:30:06 -0500
from: Bradley Stone <bvstone@xxxxxxxxx>
subject: Re: Problem with open in MAILR

Doesn't it have an option to state the CCSID of the PDF to create? If
not, and you can find what command it's using to create the stream
file (if it's not native APIs), then maybe you could use CHGCMDDFT to
change the default of that command. For example, if it's using
CPYTOSTMF.

Just an idea. Otherwise I'd contact the creators of the command and
ask they put a parameter in to let you specify the CCSID of the PDF
created.

Brad
www.bvstools.com

On Wed, Aug 24, 2011 at 10:21 AM, Marvin Radding
<marvin.radding@xxxxxxxxxxxxxxxxxxxxx> wrote:
The value of QCCSID is 37. The job CCSID is 37. So that doesn't seem
to
be the problem.

Marvin

---------------------------
date: Tue, 23 Aug 2011 13:47:18 -0400
from: rob@xxxxxxxxx
subject: Re: Problem with open in MAILR

Several of us, me included, (primarily US operations) have done a
CHGSYSVAL SYSVAL(QCCSID) VALUE('37')
during the middle of the day and never experienced any ill effect.
?You

may wish to look at the archives for cautions on doing so. ?Follow
this

thread
http://archive.midrange.com/midrange-l/201012/msg00099.html

You could try a CHGJOB CCSID(37) prior to the CPYSPLF (recommended by
the
person who expresses caution in another thread).

I think somewhere I read about creating a shell stream file with the
desired ccsid and replacing that versus deleting and recreating it.


Rob Berendt
--
Group Dekko
Dept 1600
Mail to: ?2505 Dekko Drive
? ? ? ? ?Garrett, IN 46738
Ship to: ?Dock 108
? ? ? ? ?6928N 400E
? ? ? ? ?Kendallville, IN 46755
http://www.dekko.com





From: ? "Marvin Radding" <marvin.radding@xxxxxxxxxxxxxxxxxxxxx>
To: ? ? <midrange-l@xxxxxxxxxxxx>
Date: ? 08/23/2011 12:20 PM
Subject: ? ? ? ?Problem with open in MAILR
Sent by: ? ? ? ?midrange-l-bounces@xxxxxxxxxxxx



We have just upgraded to 7.1 and are playing with the CPYSPLF command
with the *TOSTMF option. I have created *PDF files using this command
and now I have a problem attaching those files to email. Seems that
the
PDF file created has a CCSID of 65535 that the email program abend on
with a Conversion error. I have tried many different options on the
open
API to no avail. ?Is there any way to control the CCSID that the
CPYSPLF
command uses to create the PDF? Or is there a way for the open API to
read a file with a CCSID of 65535 so it can be attached to an email
and
be readable to the recipient.

Thanks ahead of time. This is a great place to learn about the i
Series.

Marvin

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.