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



Thank you. It appears that I had *MSGLIN, since that is default, and I
didn't have *NOMSGLIN.

I use ACMS for compiling programs - and it takes forever. Um, bit of an
exaggeration there... I started running my program before I got the sfl
message that the compile had been completed. THAT message showed up IN MY
WINDOW, but the message that *I* sent from the program showed up OUTSIDE the
window - So, I think there's got to be something else wrong...

MAJOR ugly formatting... :-(
A*===================================================
A*WINDOW BOX SPECIFICATIONS
A*----------------------------------------------------------------
A R WINDOR
A WINDOW(7 30 13 45 *MSGLIN)
A OVERLAY
A WDWBORDER((*DSPATR RI) (*CHAR ' -
A '))
A RMVWDW
A USRRSTDSP
A WDWTITLE((*TEXT &TTL1))
A TTL1 14A P
A*===================================================================
A* Window dressings
A*----------------------------------------------------------------
A R WINDRS
A RTNCSRLOC(&RCD &FLD)
A WINDOW(WINDOR)
A OVERLAY
A RCD 10A H
A FLD 10A H
A 2 1'Hold on Jobq'
A PCJOBQ 1A B 2 18CHGINPDFT

Left this batch of code alone...

A*===================================================================

A* Message Subfile

A*----------------------------------------------------------------

A R MSGS

A SFL

A SFLMSGRCD(13)

A MSGK SFLMSGKEY

A MSGQ SFLPGMQ

A*===================================================================

A* Message Subfile Control

A*----------------------------------------------------------------

A R MSGC

A SFLCTL(MSGS)

A OVERLAY

A SFLDSP

A SFLDSPCTL

A SFLINZ

A 94 SFLEND

A SFLSIZ(2)

A SFLPAG(1)

A MSGQ SFLPGMQ(10)

A*===================================================================




On Mon, Apr 14, 2008 at 1:33 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:
From the manual:
The format for the keyword is specified as follows:

"WINDOW(start-line | &start-line-field start-position
| &start-position-field window-lines window-positions
[*MSGLIN | *NOMSGLIN])
[*RSTCSR | *NORSTCSR])

...
The MSGLIN parameter specifies if a window contains a message line. If
this parameter is not specified, the default is *MSGLIN. *NOMSGLIN moves
the message out of the window and places it at the bottom of the display
or where the MSGLOC keyword defines the location. The last usable line
in the window is reserved for error messages; no records are displayed
there. If the error message is longer than the line, it is truncated to
fit. "

This suggests to me that your display format may have *NOMSGLIN keyword
attached?







David Turnidge wrote:
It's been a long time since I've done this - but I have a "window"
program
that has an error subfile defined. Unfortunately, the errors show up in
the
main screen on line 24, and I want it to show up IN the window.

What am I missing?

Dave


--
---------------------------------
Booth Martin
http://www.Martinvt.com
---------------------------------




--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-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-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.