× 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 am trying to create a new DSPF source member type to distinguish DSPFs
that have been modified for a GUI tool. The idea is that if someone
goes to change a display file on the IBM I the member type of GDSPF will
tell them that there is a GUI component to this application and please
take the necessary steps to incorporate changes into the GUI tool.

I have a source member type for a display file that is GDSPF. It is a
display file and it has display file dds, but the member type happens to
be 'GDSPF'.

In RDi I am trying to open the file in the screen designer, but the only
option I have been able to get it to open with is the LPEX editor.

I have done the following:

* Created a file type under Remote Systems called .gdspf
* Created a File association for .gdspf for editors: Screen Designer
(default), and Remote systems LPEX Editor
* Created a Pasrer Association to have GDSPF parsed by the dds parser

On the Remote Systems explorer when I right click on a .GDSPF member the
only 'Open With' option I get is 'LPEX Editor' - I do not see Screen
Designer.

When I edit the source code it does not parse the source as a DDS
display file. It does recognize that a '*' in column 7 is a comment,
and that's about it.

Are there more configuration options I need to set up to handle .gdspf
as a .dspf?

Is it possible to set up a new member type in RDi that get handled as a
DSPF?

Paul

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.