RE: Display file attributes

["Tim Kredlo" <TKredlo@xxxxxxxxxxxxxxxx>]

Dan,

I am not inserting anything into the error message. The 78 character message
field is being filled from an array of 78 character messages.
The dump shows:
 CHAR(78)             ' **                             Invalid length
** '    
 VALUE IN HEX
'405C5C4040404040404040404040404040404040404040404040404040404040C995A581938
98440'X 
   41
'93859587A38840404040404040404040404040404040404040404040404040404040405C5C4
0'X     

We are on V5R2, ptf level = C4077520.

As you stated, I expected the p-field technique to yield the same results,
and was surprised when it did not.
The situation you describe below with 'output only' fields IS what I am
experiencing, but only when the 'p-field' technique is used.
It works as I want when I 'hard code' the attributes.


Thanks for the suggestions,

Tim Kredlo
Exterior Wood, Inc

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Bale
Sent: Thursday, November 04, 2004 8:26 AM
To: Midrange Systems Technical Discussion
Subject: RE: Display file attributes


By any chance, maybe in your testing, are you inserting an attribute byte
value somewhere in the MESG78 data string before you output it?  Is anything
like the following happening?

  Eval MESG78 = 'There is an ' + x'29' + 'error!'

Do a dump so we can see the hex contents of MESG78.

My vague recollection tells me that if there is an attribute byte value in
an output-only string, the attribute doesn't get reset at the end of the
display field like it normally would.  I witness this all the time in my
utility that displays a source member list in the likeness of PDM, and I
have a lot of members that have attribute byte values in the TEXT
description and, since it is output-only, the attribute "carries on" through
the following output-only fields on the display, until it hits an input
field.  Probably, it would be "turned off" by another explicit attribute
byte value.

In general, Tim, the p-field technique you are using should yield the exact
same results as using a corresponding DSPATR.

Are you current on PTFs?

hth,
db

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx / Tim Kredlo
> Sent: Thursday, November 04, 2004 10:39 AM
>
> The declaration of Mesg78_A is as follows:
> A            MESG78_A       1A  P       and "works".
>
> It just "doesn't stop working" at the end of "Mesg78", but continues 
> on past the end of the field for 82 more characters, until immediately 
> before the next field on the screen.
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
> Sent: Wednesday, November 03, 2004 7:27 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Display file attributes
>
> Tim
>
> What is the declaration of &MESG78_A - should be 1 character, right? 
> And what value do you give it?
>
> Also, is it defined in the same format where it is used?
>
> Vern

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