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




I looked at the 2 LFs already existing over this PF and both have the field IPINTEGER defined.
Since this is a once a month task and the PF is so small I'm just going to copy it into QTEMP with *MAP *DROP and hit the temp file. I only need the 1st 2 fields. I was just looking for a more elegant way to deal with the troublesome field. I had not ever run into this problem before reading a DB file from a CLP.


--
All data center service requests MUST now go through Remedy.
Please click [ HERE ] for the Remedy Action Request System.
Remember, I can't provide a precise answer to a vague question.
--


Douglas Hart - Principal Consultant


Level 3 - IBM Power i (AS/400) Tech. Support
ITT Corporation - Infrastructure Services (IS)
Americas East Data Center - Seneca Falls, NY
Voice: 315-568-7568 Doug.Hart@xxxxxxx




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Tuesday, March 15, 2011 10:55 AM
To: Midrange Systems Technical Discussion
Subject: Re: QUSRSYS/QATOCHOST file IPINTGER filed error

Doug, one option is spelled out in the message: create your own logical view over the QATOCHOST file.

Joe


When I read the file QUSRSYS/QATOCHOST in a CLP I get an error on the field IPINTGER. I'm not accessing this field. How do I define the file so it does not throw the error. Or do I just MONMSG CPF0863 right after the RCVF? Not very pretty.

DCLF FILE(QUSRSYS/QATOCHOST)
RCVF

Message ID . . . . . . : CPF0863
Date sent . . . . . . : 03/15/11 Time sent . . . . . . : 10:17:22

Message . . . . : Value of binary data too large for decimal CL variable.

Cause . . . . . : A binary field in the record has a value that is too large
for the control language (CL) decimal variable declared for that field. A CL
decimal variable of the length and decimal precision specified in the data
description specification (DDS) for the file is declared for binary fields.
Recovery . . . : Correct the data in the file that is not valid or, if the
file is a data base file, use a logical view of the file that omits the
field that is not valid.


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


This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.