Re: Adding columns to existing Infor files.

John,

What should I be comparing, and why?  Is this an attempt to find out what 
changed?  I'm not trying to find out past tense.  I am trying to decide on 
the possible negative ramifications of adding additional columns to 
existing tables.

At first I thought I dodged the bullet since Infor seemed to have used the 
logicals for all traditional RPG I/O.  Their logicals select the 
individual columns from the base tables and avoid any *ALL concept.  This 
is a good thing.  No programs would blow due to a record format level 
check.
But then it was pointed out to me that Infor does occasionally use the 
dreaded:
     select * from mytable into :mytableDS
in which mytableDS is an externally defined data structure.  At one time 
this would have only been a 'soft' error.  But many moons ago IBM came out 
with a ptf or new release which made this a hard halt if the 'from' table 
was altered and now had more columns at the end than were in the data 
structure.  Oh, it's a really simple fix.  Simply recompile the program 
and it will use the new external data structure.  I'm not saying the 
mountain is insurmountable, you just have to know whether the changes you 
want are worth the pain.

As far as any concerns about Infor screwing up the additional columns I'm 
somewhat confident they wouldn't.  For example if they do a traditional 
RPG input, modify some columns and update the row the columns I an 
interested in are outside of their control and shouldn't be altered by 
that.  But I would definitely test that out.

I have zero interest in a "needle in a haystack" solution.

Rob Berendt
-- 
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   [email protected]
To:     BPCS ERP System <bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]>
Date:   10/06/2015 08:35 AM
Subject:        Re: [BPCS-L] Adding columns to existing Infor files.
Sent by:        "BPCS-L" <bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]>



fyi - from the help text

54=Compare file member 
    Type 54 to compare file members.  You can only use this option
    on data physical files (*FILE PF-DTA) or source physical files
    (*FILE PF-SRC).  If you try to use Compare file member on any 
    other type of object, you receive an error message. 


John Rusling
Senior Developer/Analyst
Quadion LLC
Minnesota Rubber & Plastics
952.927.1419
<br />
The information in this email is confidential and may be legally 
privileged.
It is intended solely for the addressee. Access to this email by anyone 
else is
unauthorized. If you are not the intended recipient, any disclosure, 
copying,
distribution or any action taken or omitted to be taken in reliance on it, 
is
prohibited and may be unlawful.
-- 
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.



-- 
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.