It seems adding the CCSID to an character field is not yet supported in
Release 7.1.
The source files need to have a record length greater than 100. It
appears that Birgitta uses 132, based on the MARGINS(132) parameter on the
RUNSQLSTM command example in the documentation.
I create normally my source members with Record Length 132, even though my
RPG Code is between position 8 and 80 and my SQLCODE is also less than 80
characters.
But I sometimes add comments after position 80.
I'm guessing that the WRTUT8IFS source members in QRPGLESRC and QSQLSRC
should be renamed to WRTUT82IFS, based on the main procedure definition in
the RPG and statements in the SQL.
You can name the members like you want. But if you rename the RPG member, an
object with the renamed member name will be created, and you have to replace
the calls in all sources.
I normally use maximum 9 characters for member names, so I can copy the
member and add an additional character.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Donnerstag, 1. März 2018 05:50
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Write Character or XML Data to the IFS with SQL
I had success at v7r1, with one exception: Compiling WRTUT82IFS (RPG) gave
RNF0299 "Two keywords have been specified that are not allowed with each
other." per the following:
133 DCL-PI WrtUT82IFS;
134 ParUTF8 VarChar(16000000) CCSID(1208) Const;
======> aaaaa
*RNF0299 20 a 005200 Two keywords have been specified tha...
(Note that the 'aaaaa' appears directly under 'CCSID'.) The error
description is too vague. I found nothing in the v7r1 RPG Reference that
provides clues, and Google was not my friend.
Also, for others' reference (Birgitta, please confirm):
* The source files need to have a record length greater than 100. It
appears that Birgitta uses 132, based on the MARGINS(132) parameter on the
RUNSQLSTM command example in the documentation.
* I'm guessing that the WRTUT8IFS source members in QRPGLESRC and QSQLSRC
should be renamed to WRTUT82IFS, based on the main procedure definition in
the RPG and statements in the SQL.
I tested WRT2IFS, and it works. However, there is no conversion from EBCDIC
to ASCII. I'm not sure whether this was intended, and I need to do the
conversion myself.
Thanks again, Birgitta!
- Dan
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
