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


  • Subject: RE: Still having problems with Reference variables in DDS
  • From: Ragnar Torfi Geirsson <Rato@xxxxxxx>
  • Date: Wed, 3 Feb 1999 17:03:34 -0000

Patrick:
After reviewing the OS/400 DDS Reference V4R2 on the web, I find the
following text on USAGE:
It doesn't mention FNTCHRSET as an possible receiver of an P field.
Indicators do not work either .


4.3.12 Usage (Position 38)

Use this position to specify that a named field is an output-only or
program-to-system field. Do not make an entry in this position for a
constant (unnamed) field. 
The valid entries for printer files are: 
Entry Meaning 
blank or O 
        Output only 
P 
        Program-to-system (special output field) 
Output-only fields pass data from a program to the printer when the program
prints a record. 
A program-to-system field is a named, numeric, or alphanumeric output-only
field used to pass data between the program and the system. It is not
printed. A program can send data to the field with an output operation, but
the data is not printed. 
The following rules apply to program-to-system fields: 
*       The field is always named. 
*       Locations are not valid. 
*       Length, data type, and decimal positions are specified as for other
named fields. 
*       The program-to-system field must be specified as a parameter on a
PAGSEG, OVERLAY, GDF, LINE, or POSITION keyword within the same record
format. The program-to-system field is not a valid parameter on any other
keyword. A severe error message is issued if the field is not specified on
at least one of these keywords. 
*       Program-to-system fields can appear anywhere in the buffer. 
*       The only valid keywords for a program-to-system field are ALIAS,
INDTXT, REFFLD, and TEXT


        -----Original Message-----
        From:   Patrick Shrader [SMTP:pshrader@foodcity.com]
        Sent:   Wednesday, February 03, 1999 3:14 PM
        To:     RPG400-L@midrange.com
        Subject:        Still having problems with Reference variables in
DDS

        I posted this message earlier this week, and tried Ragnar's
suggestion.
        However, the CRTPRTF compile still tells me that it cannot find that
I have
        used &FDSC on any keyword. Does anyone use program to system values
for the
        FNTCHRSET keyword? If I can change the font of a field from my RPG
program
        on the fly I can greatly simplify a very complicated label program I
am
        working on. 

        The field LPDESC works fine. I want to convert it to the LXDESC
line.
          A          R STDLAB

          A            LPDESC        30          POSITION( &YDSC1 &XDSC1 )
          A                                      FNTCHRSET(C0A687A0
T1V10037)
           * replace C0A687A0 with &FDSC reference variable
                                                   
          A            LXDESC        30          POSITION( &YDSC &XDSC )
          A                                      FNTCHRSET( &FDSC T1V10037)
           * reference variable definitions
          A            XDSC1          5S 3P
          A            YDSC1          5S 3P
           *
          A            XDSC           5S 3P
          A            YDSC           5S 3P
          A            FDSC          10A  P
               CPD8049-**********
        * CPD5238      30        1      Message . . . . :   No valid record
found
        in source.
        * CPD8049      30        1      Message . . . . :   Field not
specified on
        a keyword.             

        Thanks in advance.



        ------------------------------------------------------------
        Patrick Shrader 
        pshrader@foodcity.com
        Systems Analyst
        K-VA-T Food Stores/Food City

        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * *
        * This is the RPG/400 Discussion Mailing List!  To submit a new
*
        * message, send your mail to "RPG400-L@midrange.com".  To
unsubscribe   *
        * from this list send email to MAJORDOMO@midrange.com and specify
*
        * 'unsubscribe RPG400-L' in the body of your message.  Questions
should *
        * be directed to the list owner / operator: david@midrange.com
*
        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.