Re: Level check question

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Which ID are you looking at?

This ID changes every time the file is created/modified
Data Base File Attributes
  Externally described file . . . . . . . . . :            Yes
  File level identifier . . . . . . . . . . . :            1121127123926

This is the ID responsible for level checks
Record Format List
                       Record  Format Level
 Format       Fields   Length  Identifier
 PDPMASTA        114      634  4BBE898C9C79B

Having said that...I don't think what you're trying to do will work.  You
may get the record format ID to remain the same.  But you'll find that the
resulting LF is now read-only.

You could add a new longer field, along with a trigger to keep them in-sync.

Or you could perhaps make use of an INSTEAD OF trigger to allow writes to
the LF.

Charles

On Tue, May 16, 2017 at 8:19 PM, Mike Cunningham <mike.cunningham@xxxxxxx>
wrote:

> I have a project coming up where I need to expand a character field in a
> physical file but for now I don’t want to increase the field length in any
> associated logical files. I created a test physical file and test logical
> with the field length set at the current size, compiled them and looked at
> the file identifier in the logical and recorded the value.  The logical
> file listed all physical file fields and the logical had blanks for the
> length so it would use the physical length. I then changed the logical to
> specify a length that matched the physical like below and compiled the
> logical and the file identifier did not change (as I expected). I then
> change the length of LNAME to 50 in the physical and did a CHGPF,
> recompiled the logical with LNAME at 18. Since the layout of the logical
> did not change I expected the file identifier to not change but it did. Is
> this normal behavior ? I was hoping I could do this and not need to
> recompile a lot of RPG applications that use this logical.
>
> A          R PERDTA
> A            SSID
> A            LNAME         18
> A            MNAME
> A            FNAME
> A            LFNAME
> A            LNAMELC
> A            MNAMELC
> A            FNAMELC
> A            LFNAMELC
> A            ADDR1
> A            ADDR2
> A            CITY
>
> Mike Cunningham
>
> ________________________________
> This email may contain confidential information about a Pennsylvania
> College of Technology student. It is intended solely for the use of the
> recipient. This email may contain information that is considered an
> “educational record” subject to the protections of the Family Educational
> Rights and Privacy Act Regulations. The regulations may be found at 34
> C.F.R. Part 99 for your reference. The recipient may only use or disclose
> the information in accordance with the requirements of the Federal
> Educational Rights and Privacy Act Regulations. If you have received this
> transmission in error, please notify the sender immediately and permanently
> delete the email.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD