× 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: Logical file Compilation on V4R1
  • From: Bob Larkin <blarkin@xxxxxx>
  • Date: Fri, 16 Oct 1998 01:01:31 -0700

WHAT ERROR MESSAGE ARE YOU GETTING? Unless we have machines with V3R2 and V4R1,
key the code in, and compile it,, we can only guess as to the problem!
Bob

Prabhu.Chella@smed.com wrote:

> I have a logical file compilation problem on V4R1,  which is compiling fine
> in V3R2 .
>
> The logical(JOIN)  code segment for  V4R1  machine  and the   V3R2
> machine is as below (Both have the exact PF field
> definitions and logical fields).
>
>                                     A             CHRG#              R
>            CHARGE  NUMBER    Which has a defn of   7P 0 in PF.
>  ..
> 0331.00        A            PCMMIN
>
> 0332.00        A            TMPCHG         7S 0       RENAME(CHRG#)
>
> 0333.00        A            CDEPT#                          SST(TMPCHG 1 2)
>
> 0334.00        A*
>
> 0335.00        A* KEY FIELDS
>
> 0336.00        A*
>
> 0337.00        A          K CDEPT#
>
> 0338.00        A          K CDSC
>
> The  field      CHRG#    7P 0  is renamed as TMPCHG and then the first two
> digits are  Substring to CDEPT#.
> This join logical gets compiled in V3R2  but it does not compile on  V4R2
> machine.
>
> These are the join logical formats
>      A* RECORD FORMAT
>      A*
>      A                                                         JDFTVAL
>
>      A          R PHLXXXXA                  JFILE(PXPCHRG PXPPRIC)
>      A                                                        TEXT('CHARGES
>  AND PRICING
>      A          J                                           JOIN(PXPCHRG
> PXPPRIC)
>      A                                                       JFLD(CHRG#
> PMCHG#)
>      A
> JDUPSEQ(PMSEQ#)
>      A*
> The physical files and the logical have exactly same field definitions in
> both V4R1 and V3R2.
>
> Can anybody tell me whether i have to go for some other alternative coding
> of the file Or i can use some other way to
> fix the problem.
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---


begin:          vcard
fn:             Bob Larkin
n:              Larkin;Bob
org:            <A HREF="HTTP://web.wt.net/~blarkin/">Larkin Computer Consulting</A>
adr:            <A HREF="http://web.wt.net/~blarkin/">Bob and Diana's Page</A>;;;Houston;TX;<A HREF="http://web.wt.net/~blarkin/">;United States
email;internet: blarkin@wt.net
title:          Systems Consultant
x-mozilla-cpt:  ;4104
x-mozilla-html: FALSE
version:        2.1
end:            vcard


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.