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



OK, it helps to re-read from the beginning.  <g>

You are using query to load records into an outfile.  It sounds like the
outfile is predefined with PF DDS source, and is NOT actually
created/defined by WRKQRY.  The outfile has a packed field defined.  So far,
so good?

It would really help to know the message ID of the "mismatched field type".
Move the cursor down to the message and press F1, and you'll see the message
ID at the top of the screen.

I'll hazard one other guess.  The field you've defined as packed in the
output file...  What is the source of this particular field?  An input file
or "Define result fields"?  If it is defined in an input file, how is it
defined?  Packed or Zoned or ???

db

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx / Glenn Thompson
> Sent: Thursday, October 28, 2004 2:02 PM
>
> The source file is a flat-file, externally-defined.  The target file has
> a packed field.
>
> Dan Bale wrote:
>
> >When you said COMP, I thought you were talking COBOL, and
> comparing that to
> >P-type field.
> >
> >Defining a packed field in query?  Let me ask, is this an
> externally-defined
> >file you are querying?  It sounds like you might be dealing with a
> >"flat-file" with no external definition and, so, you have packed
> data in a
> >long character field you need to extract.  Is that it?
> >
> >Otherwise, I have no idea why you need to explicitly define a
> packed field.
> >
> >db
> --
>
> Glenn Thompson


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.