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



Okay, 

     I understand, and in the words of the support ceneter it works as designed 
:-(  Although I relly don't think Rochester intended for it to treat Blanks as 
Nulls and see D4C9404040 as D4C9.  So you might open an APAR, but since it's 
been this way since at least V4R5 (oldest I have) not sure you will be able to 
get it fixed. 

     QCMDEXEC might work right, but the CMD processor just does not appear as 
if it's going to do what you want in a CLP.  Other option migt be an OPNQRYF to 
do the include and then the copy..

       JMS..

See.. 
http://as400bks.rochester.ibm.com/html/as400/v4r5/ic2924/index.htm?info/db2/rbal3mst02.htm

Each field value specified is converted from the displayed format to the type 
defined by the field in the from-file record format. <b> If a value is 
specified for a character field that is shorter than the actual field, the 
comparison is performed using only the length of the character string value. 
</b> A value specified for a character field is converted from the current job 
CCSID to the CCSID of the from-file field. A value specified for a numeric 
field is converted to an internal form with the same number of decimal numbers 
defined in the DDS for the field. For DBCS graphic fields, specify the input 
string (DBCS data) within SO-SI characters. The SO-SI pair is removed from the 
input string and the remaining DBCS data is converted from the associated DBCS 
CCSID of the current job to the DBCS CCSID of the DBCS graphic field. If a 
value is either too large for the corresponding record format field definition, 
or cannot be converted to the type required for the field, an error message is 
sent and the copy operation is not done. 



-----Original Message-----
From: pnelson@xxxxxxxxxx
Sent: Oct 8, 2004 9:08 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: CPYF question

I've given up. I'm going to try this approach:

http://www.itjungle.com/mgo/mgo082802-story01.html


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx





"Dan Bale" <dbale@xxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/08/2004 07:56 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: CPYF question


JMS wrote:
> Did I enter this thread to late and miss something .....

I think so.  <g>  Paul already responded, so I'll just reiterate that we
*know* (but absolutely dislike) that CPYF has the behavior of returning
results for (TxSuf LIKE 'MI%') when specifying INCREL((TxSuf *eq &Var5)) 
and
&Var5 is a 5-byte alpha with a value of 'MI   '.  In my data, the 
following
will be returned:

  TXSUF
  -----
  MI
  MIDET
  MIFLN
  MISAG

The question becomes, how do I code CPYF INCREL so that it only returns an
EQUAL hit?

db




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.