Also check that your not clobbering any of your subfile control hidden
fields that are used to position the subfile records and such with
non-numeric data. This will happen most times when you use the
DDS-ALL-FORMATS clause which the record formats to redefine the display
record. Another problem comes from defining the subfile as a window and
displaying it outside of the display area. I have had errors so severe
that I would get an abend and be signed off immediately. It has always
helped to step through the write statement in debug and display my field
values to find the culprit.

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent: Tuesday, September 23, 2008 1:39 PM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] file status question

that's what i thought. thanks guys!

Thanks,
Tommy Holden



From:
"Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx>
To:
"COBOL Programming on the iSeries/AS400" <cobol400-l@xxxxxxxxxxxx>
Date:
09/23/2008 01:36 PM
Subject:
Re: [COBOL400-L] file status question
Sent by:
cobol400-l-bounces@xxxxxxxxxxxx



Yup, its been my experience that a 9N is usually due to a failure to
properly initialize all fields in a subfile record or the subfile
control record.

Terry

date: Tue, 23 Sep 2008 10:22:47 -0500
from: Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
subject: [COBOL400-L] file status question

we recently had a patch we received from an external vendor that has
broken an interactive program and i would like to be certain about the

error before i report it and get the run-around on the root cause.
the
file status being reported is "9N" i believe this is a subfile/fisplay

file error based on what i could find doing a google search. is that
a
correct assumption?

Thanks,
Tommy Holden

Confidentiality Notice:

The preceding e-mail message (including any attachments) contains
information that may be confidential, protected by applicable legal
privileges, or constitute non-public information. It is intended to be
conveyed only to the designated recipient(s). If you are not an intended
recipient of this message, please notify the sender by replying to this
message and then delete it from your system. Use, dissemination,
distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.



--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/cobol400-l.



--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/cobol400-l.


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