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



Rob,

Quick update on this. Starting Feb 1, 2016 LX 8.3 programs started getting compiled at V7R1 and BMR explosions are saved and shipped at V7R1. The older BPCS versions will be moving up to V7R1 also in the coming months with the BPCS 8.x versions coming first.

Regards,
Mark Larson, Infor LX Development

-----Original Message-----
From: BPCS-L [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, February 8, 2016 8:43 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Why still 6.1?

Since Infor announced End of Support for 6.1 the same time as IBM, 2015-09-30, then why do they still compile down to that level?

DSPOBJD
Object . . . . . . . : ACP100D2
Library . . . . . : M83ALL5
User-defined information:
Attribute . . . . . . . . . . . . . : 83.05.001
Creation information:
Creation date/time . . . . . . . . . : 11/03/15 14:46:18
Created by user . . . . . . . . . . : KOSIKK
System created on . . . . . . . . . : USALID21

DSPPGM
Release program created on . . . . . . . . . . : V7R1M0
Release program created for . . . . . . . . . : V6R1M0

Oh, I see. The program was created 11/03/15, but the module that the program was built off of was from much earlier.
Module creation date/time . . . . . . . . . . : 03/24/15 15:52:30
Source file change date/time . . . . . . . . . : 03/24/15 15:52:16



Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.