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



The added D-spec seems to have fixed the problem. Thanks for all your
help!

Mark Bazer
Director, Information Systems
Dyno LLC
954-971-2910 ext. 202


message: 1
date: Thu, 12 Nov 2009 08:50:15 -0600
from: Booth Martin <booth@xxxxxxxxxxxx>
subject: Re: WORKSTN file problem

Add a line:

D UpdateF6 N overlay(DspInds:22)

And then in the RPG code where *in22 is affected, affect UpdateF6 instead.




message: 3
date: Thu, 12 Nov 2009 10:23:16 -0500
from: Terrence Enger <tenger@xxxxxxxxxxxxxxxx>
subject: Re: WORKSTN file problem

Mark,

The solution, I think is already in the earlier responses. Let me
summarize what I think I understand.

The failure to display the expected "F6: Update" arises because your
code sets on rpg indicator 22, but the combination of DDS specification
INDARA and the RPG specification INDDS() means that your indicator never
reaches the display file.

Your code is close to working. Just a couple of additions ...

On Thu, 2009-11-12 at 08:39 -0500, Mark.Bazer@xxxxxxxxxxxxxxxxxxx wrote:
Here is the F-spec from the WORKSTN file and the related D-specs:
FIMS01FM cf e workstn INDDS(DspInds)

D DspInds ds
D Exit N overlay(DspInds:03)
D Accept N overlay(DspInds:06)
D Cancel N overlay(DspInds:12)
D AdvertiseF6 N overlay(DspInds:22)
*
C/free
AdvertiseF6 = *ON ; // or *OFF, depending on something you know
// but I don't
// Some time thereafter, comes WRITE or EXFMT or whatever.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.