User Defined Fields
Davide Roveda <[email protected]>
| Newsgroups | gmane.comp.systems.as400.bpcs |
|---|---|
| Message-ID | <CAFuhPrtvvstont5GZSEVxxF8irZN=MM13bWOxi_+Lwrihx+GVw@mail.gmail.com> |
Hello I suppose that the user defined fields referred for V8.3.4 is the UDF function. Option 49 is added into 19 master file maintenance in order to add as many field customer needs, up to 999 sequences. Via SYS108 you can define prompted fields for: Table Master Item Vendor Customer Date Language Warehouse Facility Currency Text And free field Alfa & numeric For any of the 19 master files. Is also easy to add the option "49" to be called via Exit point for the defined master file(s) handling, avoiding the double input from the user with minimum effort. Thanks Kind regards Davide Roveda Infor 2015-10-06 19:00 GMT+02:00 <bpcs-l-request-Zwy7GipZuJhWk0Htik3J/[email protected]>: > Send BPCS-L mailing list submissions to > bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.midrange.com/mailman/listinfo/bpcs-l > or, via email, send a message with subject or body 'help' to > bpcs-l-request-Zwy7GipZuJhWk0Htik3J/[email protected] > > You can reach the person managing the list at > bpcs-l-owner-Zwy7GipZuJhWk0Htik3J/[email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of BPCS-L digest..." > > > *** NOTE: When replying to this digest message, PLEASE remove all text > unrelated to your reply and change the subject line so it is meaningful. > > Today's Topics: > > 1. Re: Adding columns to existing Infor files. ([email protected]) > 2. Re: Adding columns to existing Infor files. (Dan Sweeney) > > > ---------------------------------------------------------------------- > > message: 1 > date: Tue, 6 Oct 2015 10:04:09 -0400 > from: [email protected] > subject: Re: [BPCS-L] Adding columns to existing Infor files. > > I had to look up in the dictionary as to what you meant, since it wasn't > inherently obvious to me. (pun intended). > It doesn't matter what you inherit, it matters what you are using. > Group Dekko (long ago known as Lyall Electric) was the 3rd customer BPCS > ever had and we're the oldest still running it. Roger came on site and > wrote one of the modules on our S/34. > We're currently running Version 8.3 Release 03 > > Oh, I get your point. We're running Version 8.3.3 and you said 8.3.4 is > where their user defined columns were added to many of the base table. I > am looking to add three timestamp columns, a 1 char, two 128 byte variable > length character, and one 28 byte variable length character that are > system maintained. Do you see that in the user defined fields in 8.3.4? > > > 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: Dan Sweeney <Dan.Sweeney-wzDqe+/[email protected]> > To: BPCS ERP System <bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]> > Date: 10/06/2015 09:30 AM > Subject: Re: [BPCS-L] Adding columns to existing Infor files. > Sent by: "BPCS-L" <bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]> > > > > What version of BPCS/LX did you inherent? > > -----Original Message----- > From: BPCS-L [mailto:bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of > [email protected] > Sent: Tuesday, October 06, 2015 9:19 AM > To: BPCS ERP System > Subject: Re: [BPCS-L] Adding columns to existing Infor files. > > The problem with user defined fields is multifold. One, many of the > tables I am considering do not use them. Two, many of the columns I want > to add have timestamps and whatnot and I want the system to maintain them > and I do not want to rely upon RPG tricks to overlay a timestamp into some > character column, nor do I wish to always have to translate said > conversion every time I want to query by that column. Triggers and User > Defined Functions (and maybe even a view utilizing some of those UDF's) > would take out a lot of that pain. > But what it really boils down to is that I want to add some very specific > columns without disrupting the business by having Infor programs blow up. > > > 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: Dan Sweeney <Dan.Sweeney-wzDqe+/[email protected]> > To: BPCS ERP System <bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]> > Date: 10/06/2015 09:00 AM > Subject: Re: [BPCS-L] Adding columns to existing Infor files. > Sent by: "BPCS-L" <bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]> > > > > Depending on the version of BPCS/LX you are implementing in ERPLX 8.3.4 > Infor has added some user defined fields for a lot of the master files to > help rectify the use of extension files and doing data base changes to the > > base physical files. > > -----Original Message----- > From: BPCS-L [mailto:bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of > [email protected] > Sent: Tuesday, October 06, 2015 8:55 AM > To: BPCS ERP System > Subject: Re: [BPCS-L] 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. > > -- > 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. > > -- > 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. > > > > > > ------------------------------ > > message: 2 > date: Tue, 6 Oct 2015 14:21:18 +0000 > from: Dan Sweeney <Dan.Sweeney-wzDqe+/[email protected]> > subject: Re: [BPCS-L] Adding columns to existing Infor files. > > Rob - also in 8.3.4 Infor added a lot of what are looking for as in date > stamping etc. - if you can tell me exactly what you are adding (field > content) and to which files I can look it up in 8.3.4 for you. > > -----Original Message----- > From: BPCS-L [mailto:bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of > [email protected] > Sent: Tuesday, October 06, 2015 10:04 AM > To: BPCS ERP System > Subject: Re: [BPCS-L] Adding columns to existing Infor files. > > I had to look up in the dictionary as to what you meant, since it wasn't > inherently obvious to me. (pun intended). > It doesn't matter what you inherit, it matters what you are using. > Group Dekko (long ago known as Lyall Electric) was the 3rd customer BPCS > ever had and we're the oldest still running it. Roger came on site and > wrote one of the modules on our S/34. > We're currently running Version 8.3 Release 03 > > Oh, I get your point. We're running Version 8.3.3 and you said 8.3.4 is > where their user defined columns were added to many of the base table. I > am looking to add three timestamp columns, a 1 char, two 128 byte variable > length character, and one 28 byte variable length character that are > system maintained. Do you see that in the user defined fields in 8.3.4? > > > 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: Dan Sweeney <Dan.Sweeney-wzDqe+/[email protected]> > To: BPCS ERP System <bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]> > Date: 10/06/2015 09:30 AM > Subject: Re: [BPCS-L] Adding columns to existing Infor files. > Sent by: "BPCS-L" <bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]> > > > > What version of BPCS/LX did you inherent? > > -----Original Message----- > From: BPCS-L [mailto:bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of > [email protected] > Sent: Tuesday, October 06, 2015 9:19 AM > To: BPCS ERP System > Subject: Re: [BPCS-L] Adding columns to existing Infor files. > > The problem with user defined fields is multifold. One, many of the > tables I am considering do not use them. Two, many of the columns I want > to add have timestamps and whatnot and I want the system to maintain them > and I do not want to rely upon RPG tricks to overlay a timestamp into some > character column, nor do I wish to always have to translate said > conversion every time I want to query by that column. Triggers and User > Defined Functions (and maybe even a view utilizing some of those UDF's) > would take out a lot of that pain. > But what it really boils down to is that I want to add some very specific > columns without disrupting the business by having Infor programs blow up. > > > 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: Dan Sweeney <Dan.Sweeney-wzDqe+/[email protected]> > To: BPCS ERP System <bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]> > Date: 10/06/2015 09:00 AM > Subject: Re: [BPCS-L] Adding columns to existing Infor files. > Sent by: "BPCS-L" <bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]> > > > > Depending on the version of BPCS/LX you are implementing in ERPLX 8.3.4 > Infor has added some user defined fields for a lot of the master files to > help rectify the use of extension files and doing data base changes to the > > base physical files. > > -----Original Message----- > From: BPCS-L [mailto:bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of > [email protected] > Sent: Tuesday, October 06, 2015 8:55 AM > To: BPCS ERP System > Subject: Re: [BPCS-L] 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. > > -- > 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. > > -- > 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. > > > > ------------------------------ > > Subject: Digest Footer > > -- > This is the BPCS ERP System (BPCS-L) digest 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. > > > > ------------------------------ > > End of BPCS-L Digest, Vol 13, Issue 35 > ************************************** > -- 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.